4 Project Management Flashcards
PM Software Desktop
One project manager Sophisticated software more responsive better graphics License costs incurred Collaboration limited
PM software web baaesy
Can be accessed through browser Multiple users can access at once Documents stored centrally One version maintained Can’t be used offline Graphic quality not as good as desktop
Single user
Usually desktop systems
Appropriate for small projects
Personal
Typically for home users for small projects single user software
Simper interface
Collaborative
Several users can use at once
Web based or client-server model
Info stored on central server
Potential hazards:
Power cut Fire Flood Denial of access to premise Malware Unauthorised access to data Theft of data Corruption of data Loss of key personnel
Impacts of hazards
Loss of revenue.
Damage to organisation’s image.
Effect on other bus activity
Recovery management:
Restoration of backups. Replacement of hardware Reinstallation of software. Emergency replacement of key personnel Emergency office accomodation
Recovery mngmg 2
Resources needed to recover must be planned for.
Recovery point objective (RPO) It’s the estimated max amount of time that the business activity has to recover systems and resume operations.
Know how long recovery would take.
Maximum tolerable downtime (MTD) should be considered. It’s the max time a business activity could tolerate not having essential system functionality.
Backed up data should be tested regularly to ensure the backup process has succeeded and data is accessible.
Full systems restorations should be tested periodically by attempting to restore whole server backups onto a clean server and testing them.
Prototype dev Evolutionary prototyping adv
Evolutionary/Incremental prototyping:
Iterative approach
Initial prototype developed, reviewed, and refined according to requiremts and feedback
Problems identified early in process.Cheaper to make changes in early stages than later.
Requirements can be clarified and refined
End users more involved in process, so more valuable feedback.
Developers have better understanding of expectation due to feedback.
In evolutionary prototyping, users can get used to using parts of system before whole, so need for bulk-training is reduced.
Prototype dev Throwaway prototyping
Throwaway/rapid prototyping:
Prototype is discarded and doesn’t become part of the the final product
requirements fine tuned in developemnt
more cost effective
when
Short time 9( (2-3 months) Yes requirements User involved Less technical risk budget is high enough to afford designers for modeling along with the cost of automated tools for code generation
adv
Flexible adaptable Reduces risk Each phase prioritize client // user needs Less ppl, +productivity strict deadlines
disadv
Requirement analysis may be rushed so prototypes aren’t reflection of expectations
Users get new ideas when
seeing prototypes and can lead to disappointment when the features can’t be funded. (Called feature creep)
Initial costs of developing prototype is high compared to traditional designs.
In rapid prototyping, the prototype can become rushed and may have design
In throwaway, when users see a working interface, they don’t realise effort time needed, long feedback process if regular changes wanted by user
No small
strict deadlines
Not all applications compatible with rad
Developers need to be committed to deliver on time
Reduced features due to time boxing, where features are pushed to a later version to finish a release in short period
No documentation
High skill designers developers
Software dev: Rapid application development adv
Uses prototyping to develop a system in a short time frame.
Requirements gathered through a focus group.
This type of user involvement is known as Joint application development (JAD).
Less time spent on planning and design and more emphasis put on development stage.
Strict deadlines there throughout development.
when adv disadv
High level of user involvement so end solution more suitable for end users
Users often not sure of the requirements so evolutionary approach allows for requirements to evolve.
Over ambitious requirements quickly realised and simplified
Strict deadlines prevent feature creep
Less time spent on design, more on development.
Software application frameworks allow users to be involved in configuring layouts
Software dev: Rapid application development disadv
Uses prototyping to develop a system in a short time frame.
Requirements gathered through a focus group.
This type of user involvement is known as Joint application development (JAD).
Less time spent on planning and design and more emphasis put on development stage.
Strict deadlines there throughout development.
Requirements not clearly specified so final solution may not meet needs of entire organisation.
Users required throughout the project which may lead to work overload for users or need for temporary staff
System structure may be compromised leading to instability as focus is on User Interface and getting system developed quickly.
System structure may be compromised leading to instability as focus is on User Interface and getting system developed quickly.
System structure may be compromised leading to instability as focus is on User Interface and getting system developed quickly.
System structure may be compromised leading to instability as focus is on User Interface and getting system developed quickly.
System structure may be compromised leading to instability as focus is on User Interface and getting system developed quickly.
sofwtare dev : waterfall
requrienmst design implementation verification mianatenece
when adv disadv
when
require dont change
not complicated
short/small project
stable environment
tech and tools are stable
resources are available / trained
projects where making changes to the initial plan can be very expensive
consumer does not plan to actively participate in the development process, but will evaluate the result
projects that migrate from one platform to another, that is, the requirements remain the same
User requirements gathered at beginning.
Interface and structure designed during design stage. System programmed in implementation stage.
Verification confirms if user requirement are met
Problems discovered are corrected in maintenance stage.
ez measure progress
carefeul planning reduce issues
docuementation
disadv
error only fix in that phase
start late
docuenation time consuming
no client feesback
strict manageent
rely on clear requirements
Computer-aided design (CAD) involves use of computers to design physical products.
adv disadv
adv
Expensive prototypes not necessary as stress testing
can be carried out on models
CAD drawings can be modified and enhanced wout manufacturing
List of required materials automatically produced by CAD drawings.
List of required materials automatically produced by CAD drawings.
Reuse designed components
Fewer designers required so is cheaper.
Manufacturers drawings can be created seamlessly.
disadv
loss job , employee reskilling
testing using model doesnt provide same results as testing using prodict so at least one protype needed
User can experience 3D model but it isn’t same as experiencing real thing.
CAD software is complex so highly trained staff needed
high initial cost of softaware
Designs developed by CAD will include errors made by designer.
designs limited to vector obj
