Conduct of IT projects开展项目.ppt

SPM Selection of project approach Software Project Management4th Edition Selection of an appropriate project approach Selection of project approaches In-house development: most of these issues resolved by IS planning and standards Software houses: more applicable as different customers have different needs Selection of approach governed by: uncertainties of the project properties of application to be built General approach Look at risks and uncertainties e.g. are requirement well understood? are technologies to be used well understood? Look at the type of application being built e.g. information system? embedded system? criticality? differences between target and development environments? Clients’ own requirements need to use a particular method Choice of process models ‘waterfall’ also known as ‘one-shot’, ‘once-through’ incremental delivery evolutionary development Also use of ‘agile methods’ e.g. extreme programming Waterfall Waterfall the ‘classical’ model imposes structure on the project every stage needs to be checked and signed off BUT limited scope for iteration V-process model Evolutionary delivery: prototyping ‘ An iterative process of creating quickly and inexpensively live and working models to test out requirements and assumptions’ Sprague and McNurlin main types ‘throw away’ prototypes evolutionary prototypes what is being prototyped? human-computer interface functionality Reasons for prototyping learning by doing improved communication improved user involvement a feedback loop is established reduces the need for documentation reduces maintenance costs i.e. changes after the application goes live prototype can be used for producing expected results Prototyping: some dangers users may misunderstand the role of the prototype lack of project control and standards possible additional expense of building prototype focus on user-friendly interface could be at expense of machine efficiency Other ways of categorizing prototyping what is being