4.2 Investigation & Analysis

In this section you will research and analyse all the information you need in order to design

and build the system.

You will need to:

Produce a project plan,
- breaking down the project into tasks and sub tasks
- with estimated completion dates.
- Using EXCEL to make a Gannt chart (Video)
Keep a log of the project record progress against your plan
Fact Finding:
- Request at least one formal interview.
  - Keeping copies of formal replies
  - Plan a detailed non linear interview
  - Conduct and record the interview
- Analyse the interview to extract the required information
  - Also, analyse the results of other types of fact finding
- What other methods of Fact Finding will you employ?
  - Questionnaires,
  - observation,
  - document analysis,
  - focus groups,
    - etc
Identify current processes using appropriate diagrams
- - Systems Map / Boundary Diagram
- Data Flow Diagrams (DFD),
- Systems Flow Charts
- Entity Relationship Diagrams (ERD)
Detail Hardware and Software requirements
- - Justify why this particular H/W & S/W is needed
  - Include a file size estimate
- Data Dictionary
  - - Including all data items, data types,field size and any validation required
Detail a Requirements Specification
- 6-8 SMART targets
- (Specific Measurable Achievable Realistic Timed)
Get Client to agree and sign off for Requirements Specification

GANNT CHART

Projects need to be planed and monitored to ensure that they complete on time and within budget.

Project managers are highly paid due to their ability to save the organisation money by effeicently using the resources and people to complete the project. Delays cost money!

80% of IT projects are deemed as failures.

Failure being defined as one of the 3 following reasons:

- - - - Project completed, but over Budget Millenium dome.
        Project completed but not on time Wembley delay.
        System does not meet the user's requirements

A Gannt chart is a Project Management tool used to plan, monitor and control projects (both IT and non IT)

Requirements Specification

This is the key document at the end of the Analysis that is signed off by the user to confirm that they agree what will be developed. This is what the project costings and payment (for a software house) are based on.

If the cleient has ommitted something, it will not be included in V1 of the new system.

Mark Criteria

11-9Marks:
- - Excellent end user involvement.
  - Detailed recording of user reqs
  - All items present
  - Detailed Requiremets Specification
  - Full justification of Hardware and Software
6-8 Marks
- - Good end user involvement.
  - Recording of user reqs
  - Most items covered
  - Requiremets Specification
  - Some justification of Hardware and Software with possible ommissions
3-5 Marks
- - Some attempt at establishing end user requirements
  - Attempted Requiremets Specification, but with little justification
0-2 Marks
- - Dont even think about submitting me something this bad

Page updated

Google Sites

Report abuse