8.3.1+traditional+stages+in+developing+a+system

=8.3.1 traditional stages in developing a system=

>> –   the needs of the users of the information system
 * ** Students learn about:  ** || **  Students learn to:  ** ||
 * **  traditional stages in developing a system   **
 * ** U **nderstanding the problem
 * **P** lanning
 * ** D **esigning
 * ** I **mplementing
 * ** T **esting, evaluating and maintaining || *   recognise and apply appropriate stages in their project work
 * read and interpret the requirements for a new system in terms of:

>>  –   who the participants are

>>  –   the data/information to be used

>>  –   required information technology

>>  –   information processes
 * use a variety of design tools to help plan the structure of an information system
 * use an information system to generate information  ||

**//__TRADITIONAL STAGES IN THE DEVELOPMENT OF A SYSTEM__//** || __ **TERM** __ . || Phased Diagrams, Pilot Conversion || t he process of determining wether the existing system can be fixed or if a new system is necessary. the first examination or the first look into something || **Project management** is the discipline of planning, organizing , and managingresources to bring about the successful completion of specific project goals and objectives. ||
 * **EXPLANATION** ||
 * **S**ystem **D**evelopment **L**ife **C**ycle || The systems development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application. Examples: waterfall model (which was the original SDLC method); rapid application development ( RAD ); joint application development ( JAD ); the fountain model; the spiral model ; build and fix; and synchronize-and-stabilize. ||
 * Systems Analyst || * Describe the role of the systems analyst in the Software Development Life Cycle: A systems analyst is a person who analyses systems, determines requirements and then plans information systems. They are the problem solvers who possess strong analytical and communication skills.
 * Traditional stages: || complete the table below || U nderstanding the Problem || Prelimary Requirement, Report Analysis Report, Feasiblity ||
 * P lanning || Gantt Chart Schedule for Completion, Journal, Funding Managment, Communication Managment ||
 * D esigning || Context Diagrams, Data Flow Diagrams, System Flow Diagrams ||
 * I mplementing || Direct Conversion, Parallel Convision,
 * T esting, Evaluating and Maintaining || Test, Evalute, Maintenance ||
 * STAGE 1 || UNDERSTANDING THE PROBLEM ||
 * ** U NDERSTANDING THE PROBLEM** || * **Understanding the Problem**When a system is created their are obviously going to be some problems and issues related to it. This can happen due to an array of things but it mainly happens because of //inaccurate data//. The project development team for the information system must //determine// and then //solve the problems and issues//. At this stage, their should be a a **clear problem statement**. A **preliminary investigation** determines whether or not a quick fix can //fix the current system//, or that a //new system must be created//. //Data// should be //collected// throughout the system cycle. This data should be found so that it is efficient to the cycle by giving it the full potential to understand the problem. The **requirement report** is a statement that states the **needs of a system**. It should outline the **aims** and **objectives** of the system and //how it will benefit the organisation//.An **Analysis report** is carried out by the Sysyems Analyst that examines current processes and procedures in the current system and proposes new processes or updated processes for the proposed new/updated information system.This leads fo a **Feasibility Study** that assesses //all the constraints// involved with creating/updating the proposed new/updated information system. The Feasibility report assesses //alternative solutions// and makes a //recommendations// after considering the constraints:
 * ** T echnical** constraints
 * ** O perational** ( or **O**rganisational) constraints
 * ** E conomic** constraints
 * ** S chedule** constraints ||
 * Project plan ||  ||
 * Requirements report || The Systems analysts manages activities which aim to determine the needs fo the users of the system, participants in the system and the processes performed by the system. All of these requirements are wriiten up and published in the form of a Requirement Report. ||
 * Requirements || definition: requirements are the materials or products that are needed and are obligatory for the task to be completed ||
 * * Requirements engineering || * Research an example of a requirements engineering software application.
 * Describe its major features ||
 * scope ||  ||
 * Preliminary Investigation || means the gathering of information or facts.
 * Preliminary Investigation || means the gathering of information or facts.
 * Interview/survey users || definition: ||
 * Interview/survey participants || definition: ||
 * Project Management || Definition(exerpt from wikipedia):
 * Journals and diaries for Project Management ||  ||
 * Funding Management plan ||  ||
 * Communication Management plan ||  ||
 * Gantt chart || definition: [[image:http://image.wetpaint.com/image/2/Jzc9CH9dXYLaoIUY7Py7Tw4400 align="left" caption="tom's planner Gantt charts" link="@http://www.tomsplanner.com/"]]
 * go to Tom's Planner ( www.tomsplanner.com ), get a free account, take a tour.
 * You will need to have an account for your forthcoming projects.

[[image:http://image.wetpaint.com/image/3/_K1ukvifIYME-vzP1okNYg31695 align="left" caption="impression of Tom's Planner Gantt chart"]]What's Tom's Planner?

 * Tom's Planner, allows you to create and share Gantt Charts online with "drag and drop" simplicity. It has great ease of use and gives control back to the project manager. Watch the quick tutorial or play around with Tom's Planner for free.

View this video (1 of 4) to learn how to get started with Tom's Planner and Gantt Charts

**Key features of Tom's Planner** **This video (2 of 4) takes on a tour around Tom's Planner**
 * Create schedules with simple drag and drop actions.
 * No extensive manual, just a quick __ 3-minute tutorial <<< Please view this __
 * No installation required, just hit the 'open tool' link
 * Share your schedules online with your team
 * Viewing schedules is free, no account needed
 * Schedules are saved on your computer: private and secure
 * Include schedules in your report as an image

Now let's start a Gantt chart for the Traditional 5 Stages of Developing a System as described in the BOS IPT syllabus (video 3 of 4)

Finally, time to save, publish and share your work (video 4 of 4) ||


 * STAGE 2 - PLANNING THE SOLUTION **

|| ** P LANNING** **the project will be planned, designed, implemented, tested and evaluated.**
 * * ** Planning If the //preliminary investigation// recommends //further examination of a new system//, then a project plan must be developed. A project plan //organises the project// by specifying the: **
 * ** who **
 * **what**
 * ** how **
 * **when**
 * It must include: **


 * **a gantt chart**
 * **schedule for the completion of tasks**
 * **journal**
 * **a funding management plan and**
 * **a communication management plan.**
 * **//Information Management Software// helps individuals manage information and schedule tasks. It allows email messages to be exchanged and organised.**
 * ** //Project Management Software// contains most of the features of information management software. It is a toll that plans, manages and communicates information efficiently in a large project. An example of this toll is the gantt chart. It gives the organisation an understanding of the timing/schedule of tasks. ** ||
 * **Constraints** || A constraint is anything that can hold you back, or potentially stop you from reaching your goal.Constraints can include anything from money problems to lack of knowlage. ||
 * **Feasible** ||  ||
 * **Feasibility Study** || definition: A way to determine whether the solution is achievable, given the organization's resources and constraints.

acronym: TOES (complete the list below) discuss the importance of the Feasibility Study in the Planning stage of the SDLC: ||
 * Technical feasibility
 * Operational feasibility
 * Economic feasibility
 * Schedual feasibility
 * * ** T echnical Feasibility** || **definition:** Determines whether a proposed solution can be implemented with available hardware, software, and technical resources.


 * List the questions used to determine a solution's technical feasibility: **
 * **.Are you able to perform the task?**
 * **.Can the task be done?**
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * * ** O perational Feasibility** || **definition:** Determines whether a proposed solution is desirable within the existing managerial and organizational framework.
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * * ** O perational Feasibility** || **definition:** Determines whether a proposed solution is desirable within the existing managerial and organizational framework.
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * * ** O perational Feasibility** || **definition:** Determines whether a proposed solution is desirable within the existing managerial and organizational framework.

//**(that can relatively easily be assigned a dollar value)**// || **List the tangible benefits that affect a solution's economic feasibility:** //**(that are difficult to assign a dollar value)**// || ** **List the intangible benefits that affect a solution's economic feasibility:** ||
 * List the questions used to determine a solution's Operational feasibility: **
 * **.What is the purpose of the operation?**
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * * ** E conomic Feasibility** || **definition:** Determines whether the benefits of a proposed solution outweigh the costs. ||
 * * **Development Costs** || **List the Development costs that affect a solution's economic feasibility:**
 * Cost of development software and hardware
 * * **Ongoing operational costs** || **List the Ongoing operational costs that affect a solution's economic feasibility:**
 * * **Tangible benefits**
 * * ** E conomic Feasibility** || **definition:** Determines whether the benefits of a proposed solution outweigh the costs. ||
 * * **Development Costs** || **List the Development costs that affect a solution's economic feasibility:**
 * Cost of development software and hardware
 * * **Ongoing operational costs** || **List the Ongoing operational costs that affect a solution's economic feasibility:**
 * * **Tangible benefits**
 * * **Ongoing operational costs** || **List the Ongoing operational costs that affect a solution's economic feasibility:**
 * * **Tangible benefits**
 * * **Ongoing operational costs** || **List the Ongoing operational costs that affect a solution's economic feasibility:**
 * * **Tangible benefits**
 * * **Tangible benefits**
 * * **Tangible benefits**
 * * **Tangible benefits**
 * * **Tangible benefits**
 * * **Tangible benefits**
 * * **Tangible benefits**
 * ** Explain how a dollar value could be determined for each of the tangible benefits listed: . ** ||
 * ** **Intangible benefits**
 * ** Explain how a dollar value could be determined for each of the tangible benefits listed: . ** ||
 * ** **Intangible benefits**
 * ** Explain how a dollar value could be determined for each of the tangible benefits listed: . ** ||
 * ** **Intangible benefits**
 * ** Explain how a dollar value could be determined for each of the tangible benefits listed: . ** ||
 * ** **Intangible benefits**
 * ** . ** ** Explain how a dollar value could be determined for each of the intangible benefits listed: . **
 * ** . ** ** Explain how a dollar value could be determined for each of the intangible benefits listed: . **
 * ** . ** ** Explain how a dollar value could be determined for each of the intangible benefits listed: . **
 * ** . ** ** Explain how a dollar value could be determined for each of the intangible benefits listed: . **
 * ** . ** ** Explain how a dollar value could be determined for each of the intangible benefits listed: . **
 * ** . ** ** Explain how a dollar value could be determined for each of the intangible benefits listed: . **
 * * **cost benefit analysis** ||  ||
 * * ** S chedule Feasibility** || * ** definition: **
 * **List the questions used to determine a solution's Operational feasibility:**
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||
 * ** Identify from whom and how answers to the above questions could be obtained: **** FROM WHOM: **** HOW: **** . **** How could the answers to the above questions be compiled in order to compare the technical feasibility of different solution options? **** . ** ||

**STAGE 3 - DESIGNING THE SOLUTION** || D ESIGNING SOLUTIONS **Systems Analysts** use a structure called the //top-down//, which is a way of spliting up large tasks into smaller series of them. As the smaller problems are solved, they effectively solve the bigger problems. Types of **design tools** include **diagrams**. These diagrams allow people to understand //how the information system will actually operate:// IT documents the essential details of a system, such as //the sequence//, //process// and //precise rules// for selecting particular actions. Finally, the new system is designed based on all these diagrams, the **feasability statement** and the **analysis report**. ||
 * After an //analysis// is completed, a new system must be designed.
 * **Context diagrams** are //graphical methods of representing a system// using a //single process// together with //inputs// and //outputs//. There are three sysmbols used in context diagrams:
 * **the process** //(a circle)//
 * **the data flow** //(an arrow)// and
 * **the entities** //(a rectangle).//
 * **Data Flow Diagrams** are also graphical methods of representing a system using a //number of processes// together with //inputs//, //outputs// and //storage//. They focus on the data flow between information processes in a system.
 * System Flow Diagrams represent both the flow of data and the logic of the system but are no longer needed for the IPT syllabus.
 * Systems Analyst role in the Design phase || Responsible for the operating system and associated subsystems. Provide system-level support of multi user operating systems, hardware and software tools, including installation, configuration, maintenance and support of these systems. Identify alternatives for optimizing computer resources. ||
 * Context Digram || Context diagrams are used to represent an overview of the entire information systems.

The example below is a context diagram that represents the video borrowing process (shown in the previous data flow diagram). TEXT TEXT TEXT TEXT ||
 * The system is shown as a single process along with the inputs and outputs.
 * The external entities are connected to the single process by data flow arrows.
 * Each element represented is labelled.
 * A context diagram does not show data stores and internal processes.
 * Data Flow Diagram || Data flow diagrams represent an information system as a number of processes that together form the single system.

The Implementation stage must involve **training**. Training ensures that all participants of the system know and understand its benefits. Training can come in the form of:
 * This single system can be represented more simply using a context diagram.
 * Data flow diagrams therefore show a further level of detail not seen in the context diagram.
 * Data flow diagrams identify the
 * source of data
 * flow between processes
 * Destination
 * data generated by the system. ||
 * Analysis Report ||  ||
 * IPO Chart || An IPO chart records the input, process, and output of a process, or program module. It is commonly used when designing spreadsheet formulas, calculated fields in databases, and algorithms in programming. ||
 * || simple example is to calculate someone's age. Work backwards, starting with deciding what the output should be (Age) ||
 * || more info on the IPO charts @http://www.mckinnonsc.vic.edu.au/vceit/designtools/ipo-chart.htm ||
 * **STAGE 4 - IMPLEMENTING THE SOLUTION** ||
 * **I** MPLEMENTING || The implementation stage //**delivers** the new information system to the participants//. It involves **developing the solution** //to solve the problem//. **Conversion** involves //changing from the old system to the new system//. The four types of Conversion include:
 * **Direct Conversion** involves an //immediate change// to the new system.
 * **Parallel Conversion** involves the //old and new systems working together// for some time until the new system is ready to operate on its own
 * **Phased Conversion** involves the //gradual implementation// of the new system, by //introducing new functions// of the system //over time//.
 * **Pilot Conversion** involves the //gradual implementation// of the new system, by //introducing single/small departments within the organisation to the complete new system// //over time//.
 * **Pilot Conversion** involves the //gradual implementation// of the new system, by //introducing single/small departments within the organisation to the complete new system// //over time//.

@http://ipthsc.wetpaint.com/photo/10781700/Conversion+methods+explained
 * seminars
 * manuals
 * on the job training,
 * online training
 * peer support ||
 * Conversion Method || Methods of Conversion explained (diagram on ATLAS):

ATLAS wiki page: http://portal/myClasses/9afa17be-66b6-4a47-8daa-36d3d4216735-defaultaspx/98e817ec-cd99-4336-b4ee-deecdf3621e4-defaultaspx/core/ProjectWork/Wiki%20Library/Implementing.aspx || The **managers** are responsible for the //effective use of the new system//. They oversee the computer operation and ensure that participants and machines work properly. Once the new system is up and running, it is continally **tested** and **evaluated** and **maintained:**
 * * Direct Conversion ||  ||
 * * Parallel Conversion ||  ||
 * * Phased Conversion ||  ||
 * * Pilot Conversion ||  ||
 * Implementation Plan ||  ||
 * Training plan ||  ||
 * Use documentation ||  ||
 * ** STAGE 4 - TESTING, EVALUATING AND MAINTAINING THE SOLUTION ** ||
 * **T** ESTING, ** E VALUATING ****  A ND ****  M AINTAINING ** (completes the TEAM effort in the **S**ystem **D**evelopment **L**ife **C**ycle) || After the new system is //fully implemented//, **participants expect** the **new system to work efficiently**. **Computer Operators** perform tasks on computer equipment, such as:
 * starting up
 * monitoring
 * running jobs
 * backing up.
 * **T** ESTING, ** E VALUATING ****  A ND ****  M AINTAINING ** (completes the TEAM effort in the **S**ystem **D**evelopment **L**ife **C**ycle) || After the new system is //fully implemented//, **participants expect** the **new system to work efficiently**. **Computer Operators** perform tasks on computer equipment, such as:
 * starting up
 * monitoring
 * running jobs
 * backing up.


 * **Testing** the new systems solution to problems ensures that it works. It is also carried out throughout the system development cycle. The systems performance is tested and then evaluated.
 * The **evaluation** actually determines whether the new system is working as expected or if any changes are required. This process is on-going, which allows the chance for error and then a new solution.
 * **Maintenance** is the //modification of the system// by making //minor improvements// . While the new system is operating, participants must observe to look for deficiencies, they are then required to suggest improvements. These tasks are ongoing, they last until the system is terminated or a new system is created. ||
 * Testing ||  ||
 * * Acceptance Test ||  ||
 * Evaluation ||  ||
 * * ongoing system evaluation || identify and describe essential tasks:

evaluate long term feasibility and life of system ||
 * Monitoing performance || Watching the performance of the system financially and technically ||
 * Maintaining ||  ||
 * * ongoing system maintenance || identify and describe essential tasks:

Identifiying and implementing updates to system for better reliability and bug fixing || For example with an opensource project anyone is invited to test and help improve the project ||
 * Computer Operator ||  ||
 * Trainer ||  ||
 * Tester || Internal Or External Depending on the project