Feasibility study - PowerPoint PPT Presentation

perry-avery
feasibility study n.
Skip this Video
Loading SlideShow in 5 Seconds..
Feasibility study PowerPoint Presentation
Download Presentation
Feasibility study

play fullscreen
1 / 12
Download Presentation
Feasibility study
222 Views
Download Presentation

Feasibility study

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Feasibility study A feasibility study is a preliminary investigation of a problem. It is used to decide whether a solution is possible and what effects it might have. It includes the following -A description of the existing system -Success criteria -An outline of possible solutions -A proposed solution -A development plan -A cost/benefit anlysis

  2. Other Aspects • Technological feasibility. • Economic feasibility • Social effects • Does the organisation have the people required to run the system • Effect on the client-benefits

  3. Establishing the inputs, outputs and processing of an existing system Document Inspection helps establish the inputs and outputs

  4. An Example-Payroll Systems • Identify the inputs • Explain the processing in detail • Identify the outputs

  5. Recording the information about the current system It is very important because systems constantly evolve and programmers and analysts change. Data Flow Diagrams(DFDs) are used to graphically represent inputs, processing and outputs identified. DFDs consist of four components which are terminators(entities), processes, flow arrows and stores Draw the digrams Table 6.1 and Figure 6.3

  6. Components Of A DFD • Terminator-somebody or somewhere outside the system from or to which data flows. • Process box(shown with a circle)-represents the processing • Data store(rectangle with no vertical sides)-represents the data stored • Data flow(arrows)-each arrow is labelled to show the data moving • There are different levels of DFDs- starting from context level(level 0) which has few details, then level 1, level 2 etc

  7. Systems Flow Chart • Another method that can also be used is a Systems Flow Chart but this is normally used in the Design stage • Draw Table 6.2 and figure 6.4

  8. Examples of past scenarios

  9. Requirements Specification • Add notes

  10. Identifying problems with the current system • The diagrams above together with results from all the different fact finding methods are analysed in order to identify weaknesses • Appropriate methods of input and output are identified • Storage is also determined • Processor requirements are also determined • A requirements specification is produced(User, Hardware and Software requirements)

  11. Design The following will be designed: • Inputs • Outputs • Files and/or Databases • Processing required • Validation • A test strategy • Hardware and software specification

  12. Designing Data Collection Forms