center23002457459410012100center818008745855941009200center700007484110Jarred Buckley 201618549
Dameling centurion
9410010000Jarred Buckley 201618549
Dameling centurion
center300003207385Information systems Induvidual assignmentThird year second semester
9410036300Information systems Induvidual assignmentThird year second semester
Table of Contents
TOC o “1-3” h z u Types of SDLC approaches (1.1) PAGEREF _Toc16258065 h 1Choses SDLC approach (1.2) PAGEREF _Toc16258066 h 2SDLC phases (1.3) PAGEREF _Toc16258067 h 2Waterfall model (1.4) PAGEREF _Toc16258068 h 4Approaches of software construction and modelling (1.5) PAGEREF _Toc16258069 h 4Project and project manager (1.
6) PAGEREF _Toc16258070 h 5Reasons for project failure (1.7) PAGEREF _Toc16258071 h 5Roles of a project manager (1.8) PAGEREF _Toc16258072 h 6Class notation (1.9) PAGEREF _Toc16258073 h 6Bibliography PAGEREF _Toc16258074 h 7
Types of SDLC approaches (1.1)The SDLC (System development life cycle) approaches that I will be discussing are:
Predictive approach to the SDLC CITATION JSa166 l 7177 (J.Satzinger, et al., 2016)Adaptive approach to the SDLC CITATION JSa166 l 7177 (J.Satzinger, et al., 2016)
The predictive approach is an approach at assumes that the information needed to plan the project can be planned in advance, the system will be developed according to the productive plan.
The predictive approach is the traditional way of using the SDLC to develop a project, it can be broken down into the following stages/phases:
Project initiation
During this phase the project is identified, in addition, the problem areas of the project is identified and project approval is obtained CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Project planning
During this phase the project is planned, scheduled and organised CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Analysis
The analysis phase is used to further identify the and understand the business problem or need for the new system and how the new system will benefit and support the business processes CITATION JSa166 l 7177 (J.Satzinger, et al., 2016). In addition, the system requirements are identified in this stage CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Design
This phase deals with the structure and configuration of the new system and its components, the information obtained in the previous stage is used to create logical blueprints, structure and algorithm of the new system and its components CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Implementation
This is the stage where they system is being programmed and tested CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Development
During this stage the system is installed and put into operation CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Support
This stage is only added if a system needs to be updated and the client needs further help, normally this stage is used to support the client, create updated for the system and maintain the system CITATION JSa166 l 7177 (J.Satzinger, et al., 2016). This stage is not in all of the models it depends on the author.
The adaptive approach is used when the project needs to be more flexible and be able to change with the changing environment that it is being implemented in CITATION JSa166 l 7177 (J.Satzinger, et al., 2016). this is a more agile approach to developing a system where the functions and components of the system are not defined from the start, or the system scope changed due the continuous changing environment it is implemented in CITATION JSa166 l 7177 (J.Satzinger, et al., 2016). The phases of the adaptive SDLC approach overlap and do not flow sequentially like the predictive approach. In addition, the system is developed incrementally and continually changes CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Choses SDLC approach (1.2)The SDLC approach that I would choose for the given scenario is the adaptive SDLC approach, because this approach is more versatile and flexible then predictive approach. Damelin registration system will continually need to be updated and change as our education system changes and new courses, ways or learning etc, are discovered. Therefore, I would recommend the adaptive approach because it would be able to allow the registration system to be flexible and keep up with the change environment.
SDLC phases (1.3)The phases of the SDLC are:
Project initiation
This is when the project is initiated and approval is obtained. During this phase, the Damelin registration system will be initiated and the reason for the system will be justified. The system will then need to be approved by upper management.
Project planning
During this phase the Damelin registration system activities will be planned (Scope) and scheduled (time), the project will be organised into manageable groups and given an initiation and completion time for each activity.
Analysis
This is when further investigation will be done to determine in detail why this system is needed, what the system needs to do, how the system will do it and what resources will be need to create the system (both tangible and intangible feasibility study), in addition, the project plan and processes will be refined.
Design
During this phase all the models (logical and physical) will be developed for the system and the system components. In addition, the structure and relationships for the Damelin registration system will be defined and modelled.
Implementation
This is when the Damelin registration system will be coded and tested. Once the design stage is complete the system will need to be coded by developers and then tested, in addition, customer (Damelin staff) testing will need to happen to ensure that Damelin is happy with the system.
Development
This is when the new Damelin registration system will me installed and deployed so that it can be used. In addition, training for the new system can happen here if needed.
Support
During this phase the operators will be able to contact the developers of the system for any help if needed, in addition, if there are any upgrades to the system it will be done as maintenance (corrective, adaptive and preventative) during this phase.
Waterfall model (1.4)
Figure 1 Waterfall model drawn in MS word and sourced from CITATION DKa171 l 7177 (D.Kaufmann, 2017)Figure 1, the Waterfall model, is one of the models that can be used when using the predictive SDLC approach to develop a system CITATION JSa166 l 7177 (J.Satzinger, et al., 2016). It is best used when the scope and specification document of a project is determined from the beginning and does not change. The scope and specification documents must be detailed so that it will minimise errors. Once a phase is complete the next sequential phase will begin CITATION JSa166 l 7177 (J.Satzinger, et al., 2016).
Approaches of software construction and modelling (1.5)Two approaches of software modelling and construction are:
Structured approach CITATION Dam19 l 7177 (Damelin, 2019)Object-orientated approach CITATION Dam19 l 7177 (Damelin, 2019)
Structured approach uses SADT (Structured analysis and design technique) which can be broken down into structed design, structured analysis and structured programming CITATION Dam19 l 7177 (Damelin, 2019). This approach is used when the program/system has one beginning and one end, meaning that there is a clearly identified start and end of the project, you would use this approach with the predictive SDLC approach because the scope and specification documents have been clearly identified from the beginning CITATION Dam19 l 7177 (Damelin, 2019).
The object-orientated approach used OOP (Object-orientated programming), which means that each component of the system is seen as individual objects that interact and work together to accomplish a task CITATION Dam19 l 7177 (Damelin, 2019). object-orientated design) and OOP to develop each object that creates the system. This approach is used for very agile and flexible systems. it is a newer way of developing a system and is not as structured as the structured approach CITATION Dam19 l 7177 (Damelin, 2019).
The approach that I would recommend to use for the Damelin registration system is the object-orientated approach, because it allows for more a more flexible system that will be able to adapt and change according to the environment that it is in, in addition, it is a more effective and efficient way to develop this type of system because it is not a rigid approach. The structured approach would normally be used for more critical and security and embedded systems that do not change. Therefore, the object orientated approach is the better approach to use.
Project and project manager (1.6)A project can be defined as a temporary endeavour that is undertaken by a team to create a unique service and/or product to aid in a business problem CITATION RBu17 l 7177 (R.Burke, 2017), whereas, a project manager is an individual who will organise, plan a project and its resources and lead a team in the processes of completing that project and closing the project. a project manager is a person who manages the undertaking of a project CITATION RBu17 l 7177 (R.Burke, 2017).
Reasons for project failure (1.7)
Poor IT management and poor IT procedures
Inexperienced project manager
Undefined project management practices
Inadequate executive support for the project
Inadequate involvement from all parties
Unclear business needs and project objectives
Roles of a project manager (1.8)Internal responsibilities are:
Recruiting and training team members CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Developing the schedule for the project CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Assigning work activities to team members and monitoring CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Monitoring and controlling project milestones and deliverables CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Assessing and reporting risks and developing risk plan. CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)External responsibilities are:
Reporting the projects status and progress to the relevant parties CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Communicating and working directly with the clients and stakeholders CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Identify the resources needed and obtaining the resources needed. CITATION JSa167 l 7177 (J.Satzinger, et al., 2016)Class notation (1.9)Template
<<StereotypeName>>
ClassName::SuperClass
AttributeName:Datatype=initialValue {Property}
MethodName (Parameter-list):return typeExpression
Figure 2 Example of class notation drawn in MS word and sourced from CITATION JSa168 l 7177 (J.Satzinger, et al., 2016)Example
ITClassRegister
-StudentNumber :int {primaryKey}
-StudentName: String
-StudentSurname: String
-LectureID : Int{FlorigenKey}
+AddStudent(StudentCount)
+BookClass(ClassAvalible)
+BookLecture(LectureAvaliable)
Bibliography BIBLIOGRAPHY D.Kaufmann ed., 2017. System Planning. In: System analysis and design. USA: Cengage Learning, pp. 19-20.
Damelin, 2019. Information system Study guide. PTA: Damelin Centurion.
J.Satzinger, R.Jackson & S.Burd, 2016. Adcanced design and development concepts. In: C. Learning, ed. System analysis and design in the changing world. Mexico: Cengage Learning, p. 377.
J.Satzinger, R.Jackson & S.Burd, 2016. Project planning and project management. In: C. Learning, ed. System analysis and design in the changing world. Mexico: Cengage Learning, pp. 327-355.
J.Satzinger, R.Jackson & S.Burd, 2016. The system development life cycle. In: C. Learning, ed. System analysis and design in the changing world. Mexico: Cengage Learning, pp. 298-300.
R.Burke, 2017. Fundamentals of project management. 1 ed. China: Burke publishings.