Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHAPTER 1: INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN, SYSTEM DEVELOPMENT…
CHAPTER 1: INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN
SYSTEM DEVELOPMENT LIFE CYCLE
TESTING
This phase involves system integration and system testing, normally carried out by a Quality Assurance professional to determine if the proposed design meets the initial set of business goals
DESIGN
The third phase describes in detail, the necessary specifications, features, and operations that will satisfy the functional requirements of the proposed system which will be in place
IMPLEMENTATION
The sixth phase is when the majority of the code for the program is written and when the project is put into production by moving the data and components from the old system and placing them in the new system via a direct cutover
ANALYZE
The second phase is where teams consider the functional requirements of the project or solution. it's also where system analysis takes place
MAINTANANCE
The last phase is when end users can fine tune the system if they wish to boost performance , add new capabilities or meet additional user requirements
PLANNING
To find out the scope of the problem and determine solutions. Resources, cost, time ,benefits and other items should be considered here
DEVELOPMENT
This phase marks the end of the initial section of the process. Additionally, this phase signifies the start of production. The development stage is also characterized by instillation and change
1.2.3 Various Types of Life Cycle Models
Waterfall Model
The Waterfall Model was the first Process Model to be introduced.
It is also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.
Spiral Model
The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model. This Spiral model is a combination of iterative development process model and sequential linear development model
It allows incremental releases of the product or incremental refinement through each iteration around the spiral.
Iterative and incremental development
An incremental development process works on the basis that work is sliced into pieces (increments)
Each increment builds on top of what has gone before. Iterative development is the process of repeating and refining a cycle or way of working an iteration.
Agile Model
Agile model is a combination of iterative and incremental process models with focus on process adaptability and customer satisfaction by rapid delivery of working software product.
Agile Methods break the product into small incremental builds. These builds are provided in iterations.
Prototyping model
The prototyping model is a systems development method in which a prototype is built, tested and then reworked as necessary until an acceptable outcome is achieved from which the complete system or product can be developed.
Rapid Application Development (RAD)
Rapid Application Development (RAD) is a form of agile software development methodology that prioritizes rapid prototype releases and iterations.
Unlike the Waterfall method, RAD emphasizes the use of software and user feedback over strict planning and requirements recording.
Joint Application Development (JAD)
JAD is a software design process that brings together, in one physical location representatives from the users, sponsors, analysts, designers and developers.
JAD is to get all of the key knowledge holders into a room and flush out a suitable design.
The basic idea of the JAD is to answer all of the questions around requirements and produce an acceptable design.
1.3 Understand Project Management
1.3.2 Explain steps in project planning.
Create and Analyze Business Case
It should outline the problem, such as a lack of repeat customers or a day longer supply line than competitors and describe how this will be solved and how much monetary benefit should accrue to the organization once the project is completed.
Identify and Meet Stakeholders for Approval
Identifying project stakeholders means listing anyone who will be affected by your project, so includes the public and government regulatory agencies. For the project planning phase however, it should only be necessary to meet those who will directly decide whether the project will happen or not.
Define Project Scope
It is necessary to delineate the boundaries of your project to prevent “scope creep”, i.e. your resources going towards something that’s not in your project’s goals.
Set Goals and Objectives
The goals and objectives for your project will build on the initial objectives outlined in the business plan. At this step you will give finer detail to the initial broad ideas and set them in a project charter as reference points for your project as it proceeds.
Determine Deliverables
Deliverables are the concrete results that your project produces. One of the most important project planning steps is to decide on what these deliverables will be and who is responsible for both producing and receiving them.
Create Project Schedule and Milestones
Project schedule is a very important document that outlines when different tasks of a project are due to begin and end, along with major measurement milestones. It will be referred to when measuring project progress. It will be available to all stakeholders and should be adhered to as closely as possible.
Assignment of Tasks
Responsible for different elements of the project. Assigning tasks clearly should remove any uncertainty about roles and responsibilities on your team.
Carry Out Risk Assessment
Performing a strong assessment at the planning stage of the project. All potential risks should be identified along with their possible effect on the project and likelihood of occurring.
Project Planning - includes identifying all project tasks and estimating the completion time and cost of each
Project Scheduling - involves the creation of a specific timetable, usually in the form of chartsthat show tasks, task dependencies, and critical tasks that might delay the project. Scheduling alsoinvolvesselecting and staffing the project teamandassigning tasks to team members.Project Scheduling usesGantt chartsandPERT/CPM chartstext
Project Monitoring - requires guiding, supervising, and coordinating the project team’s workload. Project manager mus t monitor the progress,evaluate the results,and take corrective action when necessary to control the project and stay on target
Project Reporting - regular progress reports to management, users, and the project team itself
Project Management Activities
Planning
Project planning refers to everything you do to set up your project for success. It is the process you go through to establish the steps required to define your project objectives, clarify the scope of what needs to be done and develop the task list to do it.
Scheduling
- scheduling in project management is the listing of activities, deliverables, and milestones within a project. A schedule also usually includes the planned start and finish date, duration, and resources assigned to each activity. Effective project scheduling is a critical component of successful time management
Monitoring
- Project Monitoring refers to the process of keeping track of all project-related metrics including team performance and task duration, identifying potential problems and taking corrective actions necessary to ensure that the project is within scope, on budget and meets the specified deadlines
Reporting
- A project management report is a summary overview of the current status of the project. ... It is provided to all project stakeholders to help keep them up to date on the progress of the project and any pressing challenges the project may be facing.
Discuss System Development Approach
Structured Analysis :In software engineering, structured analysis and structured design are methods for analyzing business requirements and developing specifications for converting practices into computer programs, hardware configurations, and related manual procedures.
Object Oriented Analysis : Object-oriented analysis is a technical approach for analyzing and designing an application, system, or business by applying object-oriented programming, as well as using visual modeling throughout the software development process to guide stakeholder communication and product quality.
Agile/Adaptive Method : Agile software development methods lie on the adaptive side of this continuum. One key of adaptive development methods is a rolling wave approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and also allows for the milestones themselves to change.
1.3.5 Explain technique for estimating task completion times and cost
Two key features of a project are on-time and on-budget delivery.
The project manager can only fulfill these objectives if the estimates leading to the project schedule and budget are accurate.
Methods for estimating project times and costs focus on simplifying the process and breaking it down into little steps.
Work Breakdown Structure
Dividing the project into smaller tasks lets a project manager get an overview of duration and cost.
It guides a project manager through a structured process by starting with the whole project on the top level.
Task Costs
Once he has broken the project up into small tasks, the project manager can assign costs.
For equipment that he has to purchase, he can contact suppliers to get accurate estimates.
Activity Durations
The project manager can use the same method as he uses for costs to assign activity duration.
He can check with suppliers to get delivery times and use historical records to estimate how long a task takes.
Understand Project Management
Path Analysis
- In statistics, path analysis is used to describe the directed dependencies among a set of variables. ... That is, path analysis is SEM with a structural model, but no measurement model. Other terms used to refer to path analysis include causal modeling, analysis of covariance structures, and latent variable models.
Work Breakdown Structures
- A work-breakdown structure in project management and systems engineering, is a deliverable-oriented breakdown of a project into smaller components. A work breakdown structure is a key project deliverable that organizes the team's work into manageable sections.
Task Patterns
- Task Patterns collect information artefacts created and used by developers when executing software development tasks of similar kind. These artefacts are organized with respect to their meaning for the described task class.