6938512
Description
Mind Map by Tarek Azad, updated more than 1 year ago
More
|
Created by Will Wright
about 9 years ago
|
|
|
Copied by Tarek Azad
about 8 years ago
|
|
Info 1: Topic 2 - Analysis
- Key
concepts
- Problem Identification
- Is the problem worth solving?
- Time, cost,
etc.
- Time, cost,
etc.
- Is the problem the system
itself or how it is being used?
- Identify the client and the user - with their respective skill levels
- Is a new system needed or
can the problem be fixed with
maintenance of the current
system?
- Is the problem worth solving?
- Client Requirements
- What does the client want the system to do
- Resulting solution must match
what the client has asked for,
regardless of what the developer
thinks.
- Resulting solution must match
what the client has asked for,
regardless of what the developer
thinks.
- Can be conducted by formal interview,
over email or over a noted telephone
call
- What does the client want the system to do
- Input, Process & Output
- Client, User & Audience
- Client: The person who has
an ICT problem and
approaches a developer to
create a solution
- User: People who use an ICT system on a day-to-day
basis. They modify and enter data and will use the
output in some way.
- Audience: People who view the
system but don't change the data in
any way
- Client: The person who has
an ICT problem and
approaches a developer to
create a solution
- Problem Identification
- SDLC
- "Systems Development Life Cycle"
- Systems Investigation -> Analysis -> Design
-> Create Solution -> Testing ->
Changeover/Installation/Implementation ->
Maintenance -> Review/Evaluation
- "Systems Development Life Cycle"
- Analysis
- Methods
- Observation
- Applicable for reviewing users. Allows the
developer to see common mistakes made by
the workforce
- Applicable for reviewing users. Allows the
developer to see common mistakes made by
the workforce
- Interview
- Most appropriate for the client. Allows
the developer to compile client
requirements and usually only occurs
once to save the client time in the long
run
- Most appropriate for the client. Allows
the developer to compile client
requirements and usually only occurs
once to save the client time in the long
run
- Questionnaire
- Most appropriate for users. Allows them
to answer questions in their own time
and at a time that is convenient to them.
Leading to better quality of answer
- Most appropriate for users. Allows them
to answer questions in their own time
and at a time that is convenient to them.
Leading to better quality of answer
- Documentation
- Allows developer to see direct output from
the system to see it's current process and any
possible bugs that can be addressed
- Allows developer to see direct output from
the system to see it's current process and any
possible bugs that can be addressed
- Observation
- Methods
Want to create your own Mind Maps for free with GoConqr? Learn more.