Systems Life Cycle
Check Point: Systems Life Cycle
XBIS/220
Systems Development Life Cycles (SDLC) is just one model that follows the development process of analysis, design, development, and maintenance of information systems. There are many different methods and techniques used to direct the life cycle of a software development project. Each is designed for a specific purpose or reason and most have similar goals and share many common traits. Kal Toth describes typical activities performed as including the following “System conceptualization, System requirements and benefits analysis, Project adoption and project scoping, System design, Specification of software requirements, Architectural design, Detailed design, Unit development, Software integration & testing, System integration & testing, Installation at site, Site testing and acceptance, Training and documentation, Implementation, Maintenance” (Kal Toth, 1997)
One model that sticks to this main frame of system development is Ad-hoc Development. Ad hoc analysis may be used to create a report that does not currently exist or may go deeper into a static report to get details about accounts, transactions, or records. Ad hoc testing is done as a precautionary measure to ensure that there are no gaps left in a developed system before releasing it to the consumer. The drawbacks of using Ad hoc is the lack of data for metrics analysis, lack of comfort on coverage of Ad hoc testing and that the exact steps taken are difficult to record.
Another model is the Waterfall method, also called the linear sequential method. This specific model is easy to understand and supports the “define before design” and “design before code” logic. The advantages of a Waterfall method is that output is generated after each stage, therefore it has high visibility. The client and project manager gets a feel that there is considerable progress. This methodology is significantly better than the haphazard approach to develop software.
XBIS/220
Systems Development Life Cycles (SDLC) is just one model that follows the development process of analysis, design, development, and maintenance of information systems. There are many different methods and techniques used to direct the life cycle of a software development project. Each is designed for a specific purpose or reason and most have similar goals and share many common traits. Kal Toth describes typical activities performed as including the following “System conceptualization, System requirements and benefits analysis, Project adoption and project scoping, System design, Specification of software requirements, Architectural design, Detailed design, Unit development, Software integration & testing, System integration & testing, Installation at site, Site testing and acceptance, Training and documentation, Implementation, Maintenance” (Kal Toth, 1997)
One model that sticks to this main frame of system development is Ad-hoc Development. Ad hoc analysis may be used to create a report that does not currently exist or may go deeper into a static report to get details about accounts, transactions, or records. Ad hoc testing is done as a precautionary measure to ensure that there are no gaps left in a developed system before releasing it to the consumer. The drawbacks of using Ad hoc is the lack of data for metrics analysis, lack of comfort on coverage of Ad hoc testing and that the exact steps taken are difficult to record.
Another model is the Waterfall method, also called the linear sequential method. This specific model is easy to understand and supports the “define before design” and “design before code” logic. The advantages of a Waterfall method is that output is generated after each stage, therefore it has high visibility. The client and project manager gets a feel that there is considerable progress. This methodology is significantly better than the haphazard approach to develop software.