M1S2 System Development Cycle Flashcards
Methodologies or set of activities that analysts,designers, and users carry out to develop and implement information system.
System Development Life Cycle
SDLC
System Development Life Cycle
Why is it necessary to follow a specific methodology in system development?
To develop high quality or effective information systems.
To accomplish information systems on time.
The basis for the candidate system to recognize the need to improve an information system or a procedure.
Project Selection
Top management, the user, the analyst, or someone within the organization may feel the need to update existing applications or improve procedures.
Problem Definition
Environment-based ideas from the customers, vendors, government, sources, and the like.
Impetus for System Change
Force of change
Impetus
Two Sources of System Ideas
Organization based
Environment based
Major Sources of Change
OTUS GCUC
Organization-based
Organization
Top Management
User
System Analyst
Environment Based
Government
Consumer
Union
Competition
Five Stages of SDLC
Planning
Analysis
Design
Implementation
Testing and Integration/ Deployment and Maintenance/ Support
Obtain approval for the project, initiate, assess feasibility, plan, and schedule
Planning Stage
Also known as the feasibility stage
Planning Stage
Planning Stage outputs
Feasibility Report, Project Schedule.
Output of Analysis Stage
Software Requirement SpecificationDocument
Understanding business needs and processing needs
Analysis Stage
A document containing the system’s software, hardware, and network requirements.
SRS Document
Transform the SRS document into a logical structure.
Design Stage
Define solution system based on requirement and analysis decisions and processing needs
Design Stage
Conceptual frameworks and models.
Design Stage
Create a contingency, training, maintenance, and operation plan.
Design Stage
Output of Design Stage
Design Document
Design Specification Document
Construct and implement the design into source code through coding.
Implementation Stage
Coding, software product and compilers
Implementation Stage
Integrate the information system into its environment and install the new system
Testing and Deployment/Integration Stage
Combine all the modules into a training environment that detects errors and defects
Testing and Deployment/Integration Stage
Keeps the system healthy and improve
Maintenance/Support Stage
contains errors is prepared through a test plan that includes test-related tasks such as test case generation, testing criteria, and resource allocation for testing.
test report
Output of Testing and Deployment/Integration Stage
Test Report
A system project may be dropped at any time before implementation
Project Termination
Becomes more difficult (and costly) when it goes past the design phase
Project Termination
Projects are dropped after a review process
Project Termination
During this phase, the system’s threats, constraints, integration, and security are also considered.
Planning Stage
Overview of the new system and determine its objectives.
Planning Stage
Define the problem and scope of the existing system.
Planning Stage
Gather, analyze, and validate the information.
Analysis Stage
examine the information needs of end-users and enhance the system goal.
Analysis Stage
Define the requirements and prototypes for the new system.
Analysis Stage
Include all the activities such as phone support or physical on-site support for users that are required once the system is installed.
Maintenance/Support
Implement the changes that software might undergo over a period of time or implement any new requirements after the software is deployed at the customer location.
Maintenance/Support
It also includes handling the residual errors and resolving any issues that may exist in the system even after the testing phase.
Maintenance/Support
Maintenance and support may be needed for a longer time for large systems and for a short time for smaller systems.
Maintenance/Support
