2. Question 2
2.1 The weaknesses of SDLC
There are few several weaknesses of SDLC. Firstly, it only focuses on the requirements of the end user and does not meet the needs of management. It does not provide information needed to make decision making process to support the business. It is mostly use for the end user with their daily tasks. Therefore, the function of SDLC is limited.
Secondly, the design is mostly focused on the ouput . From the output wanted, the inputs are derived and processes are made. This is difficult as outputs can be frequently change. As the inputs and processes are is designed from the output, it is difficult to make changes in the phase.
Moreover, the steps-by-step process is very iterative. It is true to say that breaking the problem down into doable phases make it easier for analyst and programmers however, the issues that need totacke is not straightfoward. The issues could be unclear, complicated and complex. Thus, SDLC which makes simple assumptions such as identifying the problem, requirements and opportunities may not be suitable to resolve complexx issues. Documentation may also lead to problems. Documentation should be done for the end-user. However, the documenting process may tend to focus on the programmer aspects and it will be difficult for end-user with no knowledge of IT to grasp the technical terms and methodology used. There is also a lack of control. If the analyst is inexperience, there will be difficulty to judge the amount of resources and work needed to desing the model thus leading to wastage of resources. 3. …show more content…
Question 3:
3.1 Alternative types of system development
3.1.1 Rapid Application Development (RAD)
Rapid application development (RAD) is an object-oriented approach to system development that includes a method of development as well as software tools (Kendall & Kendall, 2006). RAD includes the end-user involvement and also can be developed more quikly with lesser cost as it has less phases in its cycle. RAD is mostly used when the business scope is well-defined and narrowed.
For RAD, there are three phases which are:
I. Requirement Planning Phase
During this phase, user,managers and IT staff members meet to discuss the objective and requirements of the system. As it in involves many levels of users, the interaction will try to solve business problems and reach business goals. This phase will ends when the everyone has reach a common ground and the management have given approval to proceed.
II. User Design
During this session, the programmers will interect with users and build models and prototypes that meets the needs of the user. This is a interactive and continuous process and as such, users will have a greater understanding of the design of the system and could put in inputs or modify and improve the system while the design is ongoing. III. Construction In this phase, users can still suggest and modiy changes to the system . This phase focuses on designing the programmes and application. IV. Cutover Cutover phase is similiar to the implementation phase in SDLC. This is the phase where the conversion of old format to new format takes place, final user testing and training for user is provided. However ,this process is more condensed and as such, the implementation is faster and less time-consuming. 3.1.2 Joint Application Development (JAD) JAD is a well-known fact finding and requirements modelling system which bring users to
2.1 The weaknesses of SDLC
There are few several weaknesses of SDLC. Firstly, it only focuses on the requirements of the end user and does not meet the needs of management. It does not provide information needed to make decision making process to support the business. It is mostly use for the end user with their daily tasks. Therefore, the function of SDLC is limited.
Secondly, the design is mostly focused on the ouput . From the output wanted, the inputs are derived and processes are made. This is difficult as outputs can be frequently change. As the inputs and processes are is designed from the output, it is difficult to make changes in the phase.
Moreover, the steps-by-step process is very iterative. It is true to say that breaking the problem down into doable phases make it easier for analyst and programmers however, the issues that need totacke is not straightfoward. The issues could be unclear, complicated and complex. Thus, SDLC which makes simple assumptions such as identifying the problem, requirements and opportunities may not be suitable to resolve complexx issues. Documentation may also lead to problems. Documentation should be done for the end-user. However, the documenting process may tend to focus on the programmer aspects and it will be difficult for end-user with no knowledge of IT to grasp the technical terms and methodology used. There is also a lack of control. If the analyst is inexperience, there will be difficulty to judge the amount of resources and work needed to desing the model thus leading to wastage of resources. 3. …show more content…
Question 3:
3.1 Alternative types of system development
3.1.1 Rapid Application Development (RAD)
Rapid application development (RAD) is an object-oriented approach to system development that includes a method of development as well as software tools (Kendall & Kendall, 2006). RAD includes the end-user involvement and also can be developed more quikly with lesser cost as it has less phases in its cycle. RAD is mostly used when the business scope is well-defined and narrowed.
For RAD, there are three phases which are:
I. Requirement Planning Phase
During this phase, user,managers and IT staff members meet to discuss the objective and requirements of the system. As it in involves many levels of users, the interaction will try to solve business problems and reach business goals. This phase will ends when the everyone has reach a common ground and the management have given approval to proceed.
II. User Design
During this session, the programmers will interect with users and build models and prototypes that meets the needs of the user. This is a interactive and continuous process and as such, users will have a greater understanding of the design of the system and could put in inputs or modify and improve the system while the design is ongoing. III. Construction In this phase, users can still suggest and modiy changes to the system . This phase focuses on designing the programmes and application. IV. Cutover Cutover phase is similiar to the implementation phase in SDLC. This is the phase where the conversion of old format to new format takes place, final user testing and training for user is provided. However ,this process is more condensed and as such, the implementation is faster and less time-consuming. 3.1.2 Joint Application Development (JAD) JAD is a well-known fact finding and requirements modelling system which bring users to