Documente Academic
Documente Profesional
Documente Cultură
• Business case:
– the justification for an information system, presented in terms of the
tangible and intangible economic benefits and costs and the technical and
organization feasibility of the proposed system.
– Tangible costs A cost associated with an IS that can be measured in dollars
and with certainty.
• E.g. hardware cost, internet services setup fee, data entry
– Intangible costs: A cost associated with an IS that can NOT be easily
measured in dollars and with certainty.
• E.g. Loss of customer goodwill
– One time cost: A cost associate with project start-up and development, or
system start-up
• User training, site preparation, new hardware
– Recurring cost: A cost resulting from the ongoing evolution and use of a
system.
• Software maintenance
Assessing project feasibility
1. Project size
2. Project structure
3. Development group
4. User group
Project risk assessment factors
Project Size and Project Structure
• Project size
– Small projects are less riskier than large projects
– Factors that increase risks
• Number of members on the project team
• Number of organisational departments involve
• Understanding the targets of the projects
• Size of programming efforts
• Project structure
– Projects with clear requirements (well structured) will have less risks than
project with messy (or ill-structured) requirements
– Factors that increase risks
• User perception to participate in effort
• Organisational, procedural & personal change resulting from the system
• Management commitment to the system
Project risk assessment factors
Development group and User group
• Development group
– Group with more experience with similar systems (technology), and
employing commonly used or standard technology will be less risky than
one employing novel or non-standard technology
– Factors that affect development group
• Familiarity with target-hardware & software development environment
(operating environments to be used )
• Familiarity with similar technology
• Familiarity with proposed application area
• User group
– A project is less risky when the user group is familiar with the system
development process and application area than unfamiliar
Building the baseline project plan (BPP)