You are on page 1of 7

CHAPTER 3

Problem Analysis and Related Work

3.1 Literature Survey:
An e-Resource refers to that material that requires computer access, whether through a
personal computer mainframe as handheld mobile device. E-Resources are used to
access information available any time on the internet. Universities/Colleges provide e-
Resources section for their students, research scholars and even for faculties so that
they may use them for their study related tasks and for research work. Some factors
are here from which we may know that to which extent students and faculties are
provided access to e-Resources section. It is also necessary that the librarian must
have the sufficient knowledge of available e-Resources so that he/she may help the
students and faculties for their usage.

3.2 Existing System/ Problem definition:
This process is manual system. This system doesn’t provide Materials to the student
properly. This no Online Queries and answers. There are no discussion forums for
student and professor. There is no guidance to the students.

3.3 Proposed System/ Solution:
To provide official & legal links of the website from which user (student) can
download resources & study materials of relevant course .Only accessible after
registering to that specific website.
Getting associated with professors of esteemed institutes & colleges.
To provide interaction between professor & students (users).
Getting associated with well-known publication house so as to students can access soft
copy of books published for future use.

The team holds discussions with various stakeholders from problem domain and tries to bring out as much information as possible on their requirements. MANUU Page 7 . The requirements are collected using a number of practices as given -  studying the existing or obsolete system and software. 3. design and maintain the software project ensuring that all the functional & user requirement. Department of CS&IT. 1.4 Methodology: Modules/Methods/Phases: SDLC SDLC stands for Software development life cycle. Problem Analysis and Related Work 3. The requirements are contemplated and segregated into user requirements. This methodology improves the quality of the software project and over all process of software development. Requirement Gathering : This step onwards the software development team works to carry on the project. It is a process that describes how to develop. goals and objective are met. system requirements and functional requirements.

Problem Analysis and Related Work  conducting interviews of users and developers. data-flow diagrams and in some cases pseudo codes. The output of this step comes in the form of two designs. MANUU Page 8 . The implementation of software design starts in terms of writing program code in the suitable programming language and developing error-free executable programs efficiently. Analysis : At this step the developers decide a roadmap of their plan and try to bring up the best software model suitable for the project. 5. Department of CS&IT. logical diagrams. Design : The inputs from users and information gathered in requirement gathering phase are the inputs of this step. System analysis includes Understanding of software product limitations. 3. The project team analyzes the scope of the project and plans the schedule and resources accordingly. 2. 4. identifying and addressing the impact of project on organization and personnel etc. Testing : After the code is developed it is tested against the requirements to make sure that the product is actually solving the needs addressed and gathered during the requirements phase. During this phase all types of functional testing like unit testing. acceptance testing are done as well as non-functional testing are also done. logical design and physical design. system testing. integration testing. learning system related problems or changes to be done in existing systems beforehand. Engineers produce meta-data and data dictionaries. Coding : This step is also known as programming phase. 3.  referring to the database or  Collecting answers from the questionnaires.

A prototype is produced at the end of the risk analysis phase. we go for implementation. V-Model. 7. A spiral model has 4 phases described below: 1. Risk analysis phase 3. MANUU Page 9 . i. Each subsequent spiral builds on the baseline spiral. Risk Analysis: In the risk analysis phase. Risk Analysis. Agile. Maintenance : Once when the customers starts using the developed system then the actual problems comes up and needs to be solved from time to time. 2. This process where the care is taken for the developed product is known as maintenance. we need to deploy the application in some server. The spiral model has four phases: Planning. Spiral Model : The spiral model is similar to the incremental model. starting in the planning phase. Evaluation phase. Requirements like ‘BRS’ that is ‘Business Requirement Specifications’ and ‘SRS’ that is ‘System Requirement specifications’. Engineering and Evaluation. Hence in this phase the development and testing is done. Problem Analysis and Related Work 6. Planning Phase: Requirements are gathered during the planning phase. Department of CS&IT. 1. If any risk is found during the risk analysis then alternate solutions are suggested and implemented. Engineering phase 4. It’s one of the software development models like Waterfall. Planning phase 2. 3. A software project repeatedly passes through these phases in iterations (called Spirals in this model). a process is undertaken to identify risk and alternate solutions. along with testing at the end of the phase. requirements are gathered and risk is assessed. with more emphasis placed on risk analysis.e. 3. Engineering Phase: In this phase software is developed. Implementation : In testing phase if client requirements are satisfied. The baseline spirals.

 Has room for customer feedback and the changes are implemented faster.  More and more features are added in a systematic way. 3. Evaluation phase: This phase allows the customer to evaluate the output of the project to date before the project continues to the next spiral. MANUU Page 10 .  Software is produced early. Problem Analysis and Related Work 4.  Control towards all the phases of development. Department of CS&IT. Diagram of Spiral model Advantages of using Spiral Model: Advantages of using Spiral model are as follows:  Development is fast  Larger projects / software are created and handled in a strategic way  Risk evaluation is proper.

 Where releases are required to be frequent.  Where the software needs continuous risk evaluation.  It is costly for smaller projects. Problem Analysis and Related Work Disadvantages of using Spiral model: Disadvantages of Spiral model are as follows:  Risk analysis is important phase so requires expert people. jsp IDE/Workbench : Eclipse (Oxygen) Database : Oracle 10g Server Deployment : Tomcat 9.  Where enough time frame is their to get end user feedback.  Is not beneficial for smaller projects.5 System Requirements: Software Requirements: Operating System : Windows or Linux(any os) User Interface : HTML. Servlets.  Requirements are a bit complicated and require continuous clarification.x Department of CS&IT. When to Use Spiral model? Spiral model is used in the following scenarios:  When the project is large.  Spiral may go infinitely. MANUU Page 11 . 3. 3.  Software requires significant changes.  Documentation is more as it has intermediate phases. CSS Client-side Scripting : JavaScript Programming Language : Java.

3. Problem Analysis and Related Work Hardware Requirements: Processor : core 2 duo Hard Disk : 160GB RAM : 1GB or more Department of CS&IT. MANUU Page 12 .