LEARNING INFORMATION SYSTEM DEVELOPMENT

PRESENTED BY:
SUDHANSHU GAUR, RAVNEET KANG, BHARAT NAHATA SHAILESH GUPTA, RUTVIK PANDYA, SONALI RATHI, TALITHA THOMAS, SHIVIKA KANCHAN

1. Definition of system 2. System development approaches systems development life cycle method (SDLC) structured analysis development method

systems prototype method

SYSTEM DEVELOPMENT LIFE CYCLE

What is SDLC? The Systems Life Cycle (SLC) is a methodology used to describe the process for building information systems, intended to develop information systems in a very deliberate, structured and methodical way Users of SDLC Systems Development Life Cycle (SDLC) is a process used by a systems analyst to develop an information system, including requirements, validation, training, and user (stakeholder) ownership.

TYPES OF SDLC
The waterfall method The iterative method

PHASES INVOLVED IN DEVELOPMENT

Feasibility- determine if the project should get the go-ahead. In case of positive result it also produces project plan.

Requirement analysis & design- includes a detailed study of business needs of the organization. Design focuses on need of programs & their interaction.


Implementation- designs are translated into code. Different programming languages are chosen for different applications. Testing tested as an individual identity as well as a whole system. Maintenance-the software should be developed to accommodate changes that could happen during the post implementation period.

SYSTEMS PROTOTYPE METHOD

Prototype: A working system to explore implementation or processing alternatives and evaluate results. Involves the user more directly in the analysis and design experience than SDLC Useful only when employed at the right time, in an appropriate manner

REASONS FOR SYSTEMS PROTOTYPE

The major problems with building information systems : SDLC takes too long The right system is rarely developed the first time Lengthy development frustrates the user Analysts get bogged down with tedious methodologies for developing systems

USEFULNESS OF PROTOTYPES
No system with the characteristics of the one proposed has yet been constructed Essential features of the system are partially known ;others are not identifiable Experience in using the system will significantly add to the requirements list The system user will participate in the development process Alternate versions of the system will evolve through experience

Prototyping process
Identify user requiremen ts

Analyze prototype input, processing , output Revise through iterative process

Implement prototype

Final conversio n

Post implementati on

maintenanc e

RAD RAPID APPLICATION DEVELOPMENT

RAD is a methodology for compressing the analysis, design, build and test phases into a series of short, iterative development cycles.

Four phases of RAD

Requirements Planning phase User design phase Construction phase Cutover phase

Advantages
Increased speed of development Increased quality

Disadvantages
Reduced scalability Reduced features

REQUIREMENT ANALYSIS
Requirement Analysis is the second and one of the most important phases of software development. Here, client requirements are gathered. If the requirement analysis is not done properly, the entire project goes for a toss in the end. Requirement Analysis has the following steps :

..

Requirement Elicitation: It is the process of gathering customer needs. Requirement Analysis: It is the process of understanding the problem and the requirements for a workable solution. Using iterative approaches, requirements are eliminated, combined and modified. The requirements are used to generate DFDs, Use Cases etc. which are used a lot in the design phase.

..
Requirement Specification: It is the process of describing what a system will do. It involves scoping the requirements so that it meets the customers vision. Requirement Management: It is the process that helps the project team identify, control and track changes to the requirements at any time as the project proceeds.

Importance of Accurate Requirement Analysis

At requirement analysis a general statement of software scope is refined into a concrete specification that becomes the foundation for all software engineering activities that follow. It is essential to establish correct requirements and specifications early in the development process to prevent errors later in the system life cycle.

Design Of System
It is the process of defining the data for a system to satisfy specified requirements. It is translation of requirements into ways of meeting them. It transform the SRS (software requirement specification) into design that implementable using some programming language. It is an iterative process which transforms the requirement into blue print for construction. The design will determines the success of d system. It is a bridge between the requirements specifications and the final solution.

Types Of System Design

Logical Design Physical Design

Logical Design
The logical design of a system pertains to an abstract representation of the data flows, inputs(source) and outputs(destination), data basis(data stores),and procedures(data flows), all in the form that meets the user's requirements. The Design covers the followings: 1. Reviews the current physical system, its data flows, file contents, volumes, frequencies, etc.. 2. Prepares output specifications that is it determines the format, content, and frequency of reports, including terminal specifications and location. 3. Prepares input specifications it determines format, content and most of the input functions. 4. Prepares edit security and control specifications. 5. Specifies the implementation plan. 6. Prepares a logical design walkthrough of the information flow, output, input, controls and implementation plan. 7. Reviews benefits, costs, targets dated and system constraints.

PHSICAL DESIGN :
Produces the Working system by defining the design specifications that specifies what the system must do. Designing of the physical system includes: 1. Design the physical system 2. Plan system implementation 3. Devise a test and implementations plan and specify any new hardware/software. 4. Update benefits, costs, conversion date, and system constraints ( legal, financial, hardware, etc.)

TOOLS AND TECHINIQUES:

FLOWCHART DATA FLOW DIAGRAMS(DFDs) DATA DICTIONARY STRUTURED ENGLISH DECISION TABLE DECISION TREE