SYSTEMS DEVELOPMENT LIFE CYCLE

System—Set of components that interact to achieve

common goal

System—Set of components that interact to achieve

common goal

www.knowladgewithfun.blogspot.com

Uploaded by RohaanFrom www.gulshancampusa.wix.com

Key Ideas

Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization.

The primarily goal is to create value for the organization.

What is a systems analyst?

What is the System Development Cycle?

Next

Responsible for designing and developing

information system

Connection between users and IT professionals

Major Attributes of the Life Cycle

The project --◦ Moves systematically through phases where each

phase has a standard set of outputs◦ Produces project deliverables◦ Uses deliverables in implementation◦ Results in actual information system◦ Uses gradual refinement

SDLC Project Phases

Planning (Why build the system? How should the team go about building it?)

Analysis (Who uses system, what will it do, where and when will the system be used?)

Design (How will the system work?) Implementation (System delivery)

A simple process for making lunch

Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project

Planning

Analysis strategy Gathering business requirements Requirements definition use cases Process modeling Data modeling

Analysis

Design selection Architecture design Interface design Data storage design Program design

Design

Construction◦ Program building◦ Program and system testing

Installation◦ Conversion strategy◦ Training plan◦ Support plan

Implementation

Processes and Deliverables

Process Product

Planning

Analysis

Design

Implementation

System RequestFeasibility AnalysisWorkplan

System Proposal

System Specification

New System and Maintenance Plan

SDLC MODELS

Waterfall model: has well-defined, linear stages of systems development and support. example: employee payroll computing, online event management system

Spiral model: shows that software is developed using an iterative or spiral approach rather than a linear approach.

Example: Microsoft operating system,Prototyping model: used for developing

prototypes to clarify user requirements.Examples : new computer making and

military machinary

Criteria for Selecting the Appropriate Methodology

Clear user requirements Familiarity with technology Complexity of system Reliability of system Time schedule Schedule visibility

INFORMATION SYSTEM ROLES

Why systems fail?

Did not support business strategies Poor planning and project management Failure to understand user requirements Poor cost estimating and benefit analysis Design defects Incompatible or inadequate technology Lack of adequate controls Unstructured, unmaintainable software

What makes successful systems?

User involvement Systems planning and project

management Developing alternative designs Functional design guides detailed design Complete, concise, and clear

documentation Using a coordinated, planned approach Post implementation reviews Designing for systems maintenance

Role of a Project Manager

The Project Manager is a person who has overall responsibility for successful planning, monitoring, control and execution of a project. Project manager will be accountable for ensuring any objectives or goals that are predetermined inorder to complete the project as and when desired by the organization.

The Project Manager collects metrics data(such as baseline, actual values for costs, schedule, work in progress, and work completed) & reports on project progress and other project Specific information to stakeholders.

1 - 19

Information Systems Roles

Business Analyst Database Administrator Systems analyst Technical Lead/Architect Application Developers Software Quality Assurance Analyst Technical Support

Role of a Business Analyst

A Business Analyst acts as a face of Customer to the Development team, most of the time. A Business Analyst should be credible enough and the team should have absolute faith in him.

Development team should be able to ask any question regarding the system and they should believe in the answers that BAs provide. If they start having doubts on the answers BAs provide they may get tempted to develop something

that is not needed by the business or spend extra time in

clarifying the doubt from various sources.

Role of a Database Administrator

A database administrator (short form DBA) is a person responsible for the design, implementation, maintenance and repair of an organization's database.

The role includes the development and design of database strategies, monitoring and improving database performance and capacity, and planning for future expansion requirements.

A database administrator (DBA) is also responsible for the performance, integrity and security of a database. Additional role requirements are likely to include planning, development and troubleshooting.

Role of a Systems AnalystA Systems Analyst is someone who works on a high level in an organization to make sure that all of the various systems and infrastructures of a non-technical nature, as well as the capabilities of the computer systems, are working as well as they can be. A Systems Analyst examines distribution of work on a project, how it is originated, how it is created, and how it is disseminated, and will be working closely with end users to ensure that the final product is up to specification, and is created effectively with little waste of time.

Role of an Application Developer

The major role of an Application Developer is to consult with the departmental heads, in order to make sure that the product developed meets the customer’s requirement.

The main responsibilities of the Application Developer are to: identify, define, and model the application requirements. define data structures and distribution to satisfy the

application solution. prepare deliverables to support the development and deployment of the solution such as application guides and test

plans. prepare deployment and post deployment plans to support

the conversion and deployment of the solution.

Role of a Quality Assurance Analyst

The Quality Assurance Analyst's role is to develop and establish quality assurance standards and measures for the information technology services within the organization. This individual will also gather and analyze data in support of business cases, proposed projects, & systems requirements.

This will include writing test plans and scripts for tracking defects and fixes in product development, software

application development, information systems, and operations systems. The QA Analyst will apply proven analytical and problem-solving skills to help validate IT processes through careful testing in order to maximize the benefit of business investments in IT initiatives.

Summary

The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation

There are six major development methodologies: the waterfall method, the parallel development method, the phased development method, system prototyping, design prototyping, and agile development.

There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.