Académique Documents
Professionnel Documents
Culture Documents
SDLC Details
Content
Requirements
Handles What Part Requirements define what the deliverable will look like and what it will do Implied needs vs. Stated Needs (Requirements) Objective: Project includes all the work required and only the work required Getting clear requirements, is most critical and is key to success / main reason to failure of the project Requirements from all stakeholders Functional Technical Cost Quality
Inherently Fuzzy Needs Identifying solutions before needs defined fully Addressing needs of wrong customers Multiple customer - Multiple needs Sol: Establish priorities and need hierarchy. Finalize priority with customer Distorting Customer Needs Gold-Plating of needs Selective Filtering of customer needs Father-knows-best approach
Scope Verification: Verifying actual product component vs. scope baseline Scope Change: Controlling changes to project scope. Change control process, configuration management, version control
Questions
Who carries out the activities? What is carried out? How is it carried out? What is the output? What tools are used?
Requirements
Requirements and Test Plan: Verifiable Requirements Requirements Management Requirements: Static and Evolving, Project Vs Product, etc. BRS (Business Requirements Specification), FS (Functional Specification) and SRS (System Requirements Specification)
Things
Class diagram
Object-oriented approach
Interaction Use case diagrams
Entityrelationship diagram
Traditional approach
Diagram 0
Context diagram
Statechart diagrams
Other OO models
DFD fragments
Other definitions
Analysis Design
Package diagram Object database scheme Design class diagram System flow chart Structure chart
Hybrid relational database scheme User-interface dialog, forms, and reports System controls Pseudocode Nodes and locations diagram
Systems Analysis
Detailing Requirements SSAD
OO Analysis
15
Employee
Tax Slab
Finance Dept
Process Payroll
Calculate Salary
Calculate Tax
Print Salary Slip
Add Employee
Update Employee
Delete Employee
New Employee Create fill joining form Employee 1st of Month Calculate Salary
(Time)
Finance
(Time)
Generate Summary
Calculate Tax
Employee Master
Salary File
Personnel
Tax Slab
1st of year
Finance
Salary Summary
Salary File
Personnel
Add Employee
Employee Master
Systems Design
Answers the question: how will the information system solve a problem? Results in a technical design
Details system outputs, inputs, and user interfaces Specifies hardware, software, databases, telecommunications, personnel, and procedures Shows how these components are related
23
System Design
High Level Design Application Design(cont) Common Functionality Functional Decomposition System Flow System Chart File / Table Design User Interface Design Detailed Design- Program Specification
Enterprise-rights management software Disaster planning: process of anticipating and providing for disasters Disaster recovery: implementation of disaster plan Approaches Hot site Cold site Incremental backup Image log
26
Implementation
Context
In-House Development
Acquisition
Implementation
Systems Implementation
30
31
User Preparation
Readying managers, decision makers, employees, other users, and stakeholders for new systems Training users
33
Training programs should be conducted for IS personnel who will be using the system
34
Testing
Unit testing: testing of individual programs Interface testing: System: testing all related systems together Acceptance testing: conducting any tests required by user Alpha testing: testing an incomplete or early version of system Beta testing: testing a complete and stable system by end users
36
Start-Up
Process of making the final tested information system fully operational Approaches
Direct conversion (plunge, direct cutover) Phase-in approach (piecemeal) Module-wise Functionality-wise Customer Segment-wise Parallel start-up
37
Start-Up (continued)
Start-Up (continued)
User Acceptance
User acceptance document: formal agreement signed by user that states that a phase of installation or the complete system is approved
40
Maintenance Context
Implementation
Maintenance Review Objective Satisfied? Develop & Implement New System Retire This System
Systems maintenance: checking, changing, and enhancing the system to make it more useful in achieving user and organizational goals
42
Types of Maintenance
Slipstream upgrade: minor upgrade Patch: fix a problem or make small enhancement Release: significant program change requiring new documentation Version: major program change with new features
45
Identifies programs to be changed Determines programmer to be assigned to task Estimates expected completion date Develops a technical description of change
For older programs, total cost of maintenance can be up to five times greater than total cost of development
47
Systems Review
Analysis of systems to make sure that they are operating as intended Often compares performance and benefits of designed system with actual performance and benefits of operational system
50