Computer Programmers Person or group of people who do the programming works. That means they convert the design of the system into computer understandable languages 2.4. System Development Methodology A system development methodology refers to the framework that is used to structure, plan, and control the process of developing an information system. A wide variety of such frameworks have evolved over the years, each with its own recognized strengths and weaknesses. One system development methodology is not necessarily suitable for use by all projects. Each of the available methodologies is best suited to specific kinds of projects, based on various technical, organizational, project and team considerations. Acceptable System Development Methodologies include Waterfall, spiral, incremental prototyping & RAD
[DBU] [College of Computing Science]  Compiled By: S. E. Page 7/21 SAD – Chap 2 Figure 2.2 Waterfall model Framework Type: Linear Basic Principles: Project is divided into sequential phases, with some overlap and splashback acceptable between phases. Emphasis is on planning, time schedules, target dates, budgets and implementation of an entire system at one time. Tight control is maintained over the life of the project through the use of extensive written documentation, as well as through formal reviews and approval/signoff by the user and information technology management occurring at the end of most phases before beginning the next phase. Strengths: Ideal for supporting less experienced project teams and project managers, or project teams whose composition fluctuates. The orderly sequence of development steps and strict controls for ensuring the adequacy of documentation and design reviews helps ensure the quality, reliability, and maintainability of the developed software. Progress of system development is measurable. Weaknesses: Inflexible, slow, costly and cumbersome due to significant structure and tight
[DBU] [College of Computing Science]  Compiled By: S. E. Page 8/21 SAD – Chap 2 controls. Project progresses forward, with only slight movement backward. Little room for use of iteration, which can reduce manageability if used. Depends upon early identification and specification of requirements, yet users may not be able to clearly define what they need early in the project. Requirements inconsistencies, missing system components, and unexpected development needs are often discovered during design and coding. Problems are often not discovered until system testing. System performance cannot be tested until the system is almost fully coded, and under-capacity may be difficult to correct. Difficult to respond to changes. Changes that occur later in the life cycle are more costly and are thus discouraged.
- Fall '19
- Systems Development Life Cycle, DBU, College of Computing Science