計算與軟件工程ii課件chapter 3initiateproject

1、Computing and SE II Chapter 3: Software Project Initiation Main Contents 1.What is software project? 2.Staffing 3.Quality Assurance 4.Measurement and Metrics 5.Software configuration management 1. What is software project? -Program and software (3) (multipliers may be bigger if the number of compone

2、nts is large) 1. What is software project? Program and Program system product (4) nPerhaps the key problem is that when we should be thinking about program system product , we continue to think about programs, and all expectations are off by an order of magnitude. qease vs. difficulties, qtime, qcos

3、ts, q nWe see only the program and forget all the other junk that must be added to make it a program system product ! 1. What is software project ? The means of project nProject qThe objective of the project to build a program system product is to make sure that all the necessary junk gets planned i

4、n. nProjects have plans: qResources nMultiple People nSchedule nBudget nOthers qSpecific work to do qDeliverables project management? nAny project with more than one person must be managed by definition nThe job of management is to make sure that the planned junk does not get left behind in the zeal

5、 to release the software when only the program in its heart has been written! Main Contents 1.What is software project? 2.Staffing 3.Quality Assurance 4.Measurement and Metrics 5.Software configuration management 2. Staffing nPeople are an organisations most important assets. nThe tasks of a manager

6、 are essentially people-oriented. Unless there is some understanding of people, management will be unsuccessful. nPoor people management is an important contributor to project failure. “Its always a people problem” 2. Staffing -Staffing Activities Selecting Staffs Organizing Teams Managing Groups Ar

7、ranging Work Environment Motivating People 2. Staffing - Selecting Staffs / Providing Leadership nPositional Power qPower derived from having a leadership position qNot always effective nPersonal Power qCharisma or personal charm qSometimes more effective than positional power 2. Staffing - Arrangin

8、g Work Environment / Office layout 2. Staffing -Motivating People / Motivation Factors 2. Staffing -Managing groups nMost software engineering is a group activity qThe development schedule for most non-trivial software projects is such that they cannot be completed by one person working alone. n“Sch

9、edule disaster, functional misfit and system bugs all arise because the left hand does not know what the right hand is doing” nTeams working on a project must communicate with one another in as many ways as possible: informally, regular project meetings email and by a shared project (electronic) wor

10、kbook. 2. Staffing -Managing groups / Group communications nGood communications are essential for effective group working. nInformation must be exchanged on the status of work, design decisions and changes to previous decisions. nGood communications also strengthens group cohesion as it promotes und

11、erstanding. The Whole Is Greater Than The Sum Of The Parts nWrong concept of a team nA team needs: q Common definition of success qAny identifiable team spirit nConsequences: qMore productivity qEnjoy more the work “The purpose of a team is not goal attainment but goal alignment” Teamicide nDefensiv

12、e management nBureaucracy nPhysical separation nFragmentation of peoples time nQuality reduction of the product nPhony deadelines nClique control Teamicide nDefensive management qTrust your team Teamicide nBureaucracy qHurts team formation nPhysical separation qPut the people that should interact to

13、gether nFragmentation of peoples time qPut the worker in only one project Teamicide nQuality reduction of the product qLess time result in lower quality nPhony deadelines qTight deadeline can sometimes be demotivating Teamicide nClique control qMiss the opportunity to keep the team together Teamicid

14、e nMost organizations dont set out consciously to kill teams, They just act that way. Team Building nthe spaghetti dinner qThe common thread is that good managers provide frequent easy opportunities for the team to succeed together. qThe best success is the one in which there is no evident managemen

15、t, in which the team works as a genial aggregation of peers. Team Building: OPEN KIMONO Team Building: OPEN KIMONO Team Building: nAchievements Main Contents 1.What is software project? 2.Staffing 3.Quality Assurance 4.Measurement and Metrics 5.Software configuration management 3.What is software qu

16、ality - Quality nThe American Heritage Dictionary defines quality as q“a characteristic or attribute of something.” nSoftware Quality qConformance to explicitly stated functional and performance requirements, qexplicitly documented development standards, q and implicit characteristics that are expec

17、ted of all professionally developed software. 3. What is software quality - ISO/IEC 9126 3.Quality management and software development 3. Quality Management Activities nQuality assurance qEstablish organisational procedures and standards for quality nQuality planning qSelect applicable procedures an

18、d standards for a particular project and modify these as required nQuality control qEnsure that procedures and standards are followed by the software development team nQuality management should be separate from project management to ensure independence 3. Reviews but when you cannot measure it, when

19、 you can not express it in numbers, you knowledge is of a meager and unsatisfactory kind; it may be the beginning of knowledge, but you have scarcely in your thoughts advanced to the stage of science.” 4. Measurement and Metrics -Measurement, Measures, Metrics nMeasurement qis the act of obtaining a

20、 measure nMeasure qprovides a quantitative indication of the size of some product or process attribute nMetric qis a quantitative measure of the degree to which a system, component, or process possesses a given attribute 4. Measurement and Metrics 3. Measurement and Metrics - Product Metrics nfocus

21、on the quality of deliverables nmeasures of analysis model ncomplexity of the design qinternal algorithmic complexity qarchitectural complexity qdata flow complexity ncode measures nmeasures of process effectiveness qe.g., defect removal efficiency 4. Measurement and Metrics - Typical Metrics Exampl

22、es nerrors per KLOC (thousand lines of code) ndefects per KLOC n$ per LOC npage of documentation per KLOC nerrors / person-month nLOC per person-month n$ / page of documentation 4. Measurement and Metrics - Example : Productivity and Process Quality Main Contents 1.What is software project? 2.Staffi

23、ng 3.Quality Assurance 4.Measurement and Metrics 5.Software configuration management 5.1 What is SCM ? -The “First Law” No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle. 5.1 What is SCM ? - Software Configura

24、tion Management, SCM nIdentify change nControl change nEnsure that change is being properly implemented nReport changes to others who may have an interest 5.1 What is SCM ? - The Software Configuration Also include software tools, such as editor, compiler, browser and so on. 5.2 Terminologies of SCM

25、 - Baselines n The IEEE (IEEE Std. No. 610.12-1990) defines a baseline as: nA specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control procedures. na baseline is a

26、 milestone in the development of software that is marked by the delivery of one or more software configuration items and the approval of these Software Configuration Items (SCIs) that is obtained through a formal technical review 5.2 Terminologies of SCM - Baselines SCIs SCIs modified Software engin

27、eering tasks Formal technical reviews SCIs approved SCIs extracted SCM controls SCIs stored Project database System Specification Software Requirements Design Specification Source Code Test Plans/Procedures/Data Operational System BASELINES : Figure 27.1 5.2 Terminologies of SCM - Repository Content

28、 Busi ness Content M odel Content V q a make facility that enables the software engineer to collect all relevant configuration objects and construct a specific version of the software. q an issues tracking (also called bug tracking) capability that enables the team to record and track the status of all outstanding issues associated with each configuration object. 5.3 The SCM Process - Auditing SCIs Change Requests SQA Plan SCM Audit 5.3 The SCM Process - Status Accounting SCIs Change Requests Change Reports ECOs Status Accounting Reporting Engineering Change Order END! 3. What is