AS11 Flashcards
Feasibility
- Establishes whether or not a project can be completed given the scope laid out.
- Is it worth it?
Economic Feasibility
- Can the project pay for the hardware, liscences, human wages and running costs in the given budget?
- What is the profit?
Time Feasibility
- Will the project be done in time? (Risk of going over budget, making a negative impression)
Technical Feasibility
- Can the project be done with the resources available?
- Is the project doable with current accessible technology?
Political Feasibility
- Does the project go against the beliefs of certain people?
- Will the media report on it in a negative light?
Legal Feasibility
- Does the project comply with the law?
- Any chance of being sued?
Project Requirements Specification
- Produced at the end of analysis.
- Outline of how to create successful project.
- Poorly defined = delays/increased costs.
Observation
- Analysts shadow employees, see how the business works.
ADVANTAGES: - Could pick up parts of system that are not obvious to customer.
- Confirms information gathered through other methods.
DISADVANTAGES:
* - Some people may feel threatened/uncomfortable.
* No guarantee that some subtle system parts will show during observation.
Questionnaire
- A set of questions about the system, normally given to staff.
ADVANTAGES: - Can be given to big population.
- Can get a large number of responses.
DISADVANTAGES:
- Hard to design.
- Requires system knowledge.
- Not all questionnaires sent out will be completed.
Existing Documentation
- Analyst gathers documents relating to new system to infer what data will need to be stored.
ADVANTAGES: - Analyst gains understanding.
- Reliable documents.
- Document trails help support the analyst’s picture of business processes.
DISADVANTAGES:
- Documents give limited view of system.
- Documents may contain sensitive information.
Interview
- Analysts pick some key stakeholders and ask targeted questions about current system.
ADVANTAGES: - Large amounts of information can be gathered.
- Interviews produce detailed responses.
DISADVANTAGES:
- Time consuming.
- Interviewees may not be truthful. Reponses need to be verified.
Requirements
- Help keep scope of project.
- Developers can be paid based on requirements.
Types of Requirements
- Interface (Where is user interaction?)
- Functional (What will the system do?)
- Performance (e.g. response times.)
Design
- Hardware/software choices.
- Data structure design.
- Input/Output design.
- Processing design.
Flowcharts/Data Flow Diagrams
- Flowcharts represent an algorithm.
- DFDs represent how a system will process information. (Multiple levels, distinction between internal/external parts)