Author of the Program: Prof., Dr.Sci. Dmitry Alexandrov

Transcription

1

2 Author of the Program: Prof., Dr.Sci. Dmitry Alexandrov General Information about Training Course: The training course Software engineering methodology is offered to students of the Master Program «System and Software Engineering» (area code ) at the Faculty of Computer Science, the National Research University - Higher School of Economics/HSE. The course is classified as a compulsory subject (М.2.Б unit / Base module [Special subject disciplines М.2] of academic year s working syllabus); it is a two module course, which is started in module #1. The duration of the course amounts to 64 class periods (both lectures and seminars) divided into 24 lecture hours and 40 seminar hours. In addition, 116 academic hours are set aside for self-studying of students. Mark check stipulated by the working syllabus consists of one endof-module test (MT, end of first module) and final examination (FE) given in the second module; Students Requirements: It is presupposed that all individuals accepted as Master Program students completed corresponding full-time Bachelor degree training programs and were selected (based on either portfolio tenders, or other core performance indices) to continue their MS education in the Program, therefore. The students should be familiar with the basics of the following training courses: a) Object-oriented analysis and programming b) The software testing methodology. The students will learn how to analyze, design, program and test software projects, gather requirements and write user stories, use cases and use case diagrams, draft user interfaces and create functional system prototypes, translate application requirements into working code, simplify complex systems using modern object-oriented analysis and design techniques and ensure software quality with both manual and automated testing techniques. Course Objectives: The training course presents the engineering discipline which is concerned with all aspects of software production from the early stages of system specification through to maintaining the system after it has gone into use. The main objective of the training course is to examine and discuss with students fundamentals and principles of Software Engineering (SE), get familiar with common methods and standards of SE, development and evolution of complex multiversion and replicated software solutions. The course is aimed to help students to develop skills that will enable them to construct software of high quality, reliable, and that is reasonably easy to understand, modify and maintain. Abstract The training course Software engineering methodology is concerned with theories, methods and tools for professional software development. It is based on the training and research materials of Ian Sommerville, professor of Software Engineering at the University of St. Andrews in Scotland. Modern software development requires the collaborative effort of a diverse team with varied skills. To be effective, team members need to understand the activities performed at each stage in the development cycle. In this course, students analyze, design, implement and test

3 applications that meet user requirements through a simulated case study. They gain hands-on experience performing each role within the development team using all the core concepts and skills necessary to engineer a successful program. Initially the course is aimed at students taking undergraduate and graduate courses and at software engineers in commerce and industry. It may be used in general software engineering courses or in courses such as advanced programming, software specification, and software design or management. Also the course is based on the Software Engineering. Methodology course and materials developed by Professor V.V. Lipaev and implemented into NRU-HSE being a part of an innovative educational program Development of an analytical competency system for innovations in business and government in The course is compliant with ISO standards and CMM/CMMI standards for industrial software development. The training materials follow the Software Engineering Education Knowledge (SEEK) knowledge insights, described in Software Engineering 2004 (SE 2004) paper book. The training structure meets the requirements of Russian and international standards of software development and the global professional standard Guide to the Software Engineering Body of Knowledge (SWEBOK) ISO/IEC TR IEEE. The course is aimed at studying the major current approaches to software engineering processes: specification, design, development, verification, validation and management of large-scale software systems. It describes the methods, platforms, technologies and tools, which are applied for all stages of life cycle and covers software requirements specification, software design, software engineering management, dependable systems development and software evolution. Training Objectives: During the two-module course Software engineering methodology, the students will: Study the place and role of software engineering, place it in a broader systems context and present the concept of software engineering processes and management. Learn the processes, techniques and deliverables that are associated with requirements engineering, system modeling, formal specification Acquire skills in software design, module development (including agile methods, software reuse, CBSE and critical systems development), integration Focus on techniques for software verification, testing, critical systems validation and further documentation Discover the importance of management topics in software engineering: managing people, cost estimation, quality management, process improvement and configuration management. At the end of the course the students will acquire theoretical and practical knowledge and will be able to use: Technical skills 1. Define software engineering and explain its importance 2. Discuss the concepts of software products and software development processes 3. Develop and write a software project proposal 4. Develop and write a Software Requirements Specification 5. Design a software system 6. Document the design of the software system

4 7. Document the implementation of a software system 8. Define CASE tools and software development environments 9. Write a Test plan 10. Explain the importance of process visibility and software design techniques 11. Conduct a software inspection and review 12. Document software testing 13. Investigate software testing, documentation and maintenance techniques for developing large software systems 14. Prepare the final report for the course Soft skills 1. Work within a team and understand team dynamics 2. Be able to effectively communicate their work (Presentation skills) 3. Be able to write a project report (report writing skills) 4. Be able to reflect on their own work as well as the work of others (evaluate their experience) I. Topic-wise curricula plan (accompanied with suggested themes of seminars) Audience Hours Course Hours, Topic Name Self Study Total Practical Lectures Studies Module 1 (28 hrs). Software engineering values, processes, architectural design 1 Software engineering fundamentals 2 Software process models 3 Project management activities 4 Software requirements 5 Requirements engineering processes 6 System models and architecture 7 System design Module 1, totally: Module 2 (32 hrs). Software development, validation and testing, management 8 Software development 9 Software reuse and evolution 10 Verification and validation 11 Software testing 12 Managing people and cost estimation

5 13 Software risk management 14 Quality management, process improvement 15 Configuration management Module 2, totally: TOTAL: II. Basic book(s) and/or reader(s) (Publications) Books: Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., [ * original - in Russian] Липаев В.В. Программная инженерия. Методологические основы. Учебник. М.: ТЕИС, Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) TECHNICAL REPORT ISO/IEC TR IEEE First edition ; CMMI for Development, Version 1.2, CMU/SEI-2006-TR-008 ESC-TR ; Ullman David G. Mechanical Design Failure Analysis: With Failure Analysis System Software (Mechanical Engineering), Gilb Tom. Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Elsevier Butterworth-Heinemann, Bird John. Engineering Mathematics Pocket Book. Newnes, Software Engineering Inst. Carnegie Mellon Univ. The Capability Maturity Model: Guidelines for Improving the Software Process. SEI, Bernstein Michael E., Braude Eric J. Software Engineering: Modern Approaches. Wiley; 2 edition, Ghezzi Carlo, Jazayeri Mehdi and Mandrioli Dino. Fundamentals of Software Engineering (2nd Edition), Pfleeger Shari Lawrence and Atlee Joanne M. Software Engineering: Theory and Practice (4th Edition). Prentice Hall, Kutz Myer. Eshbach's Handbook of Engineering Fundamentals Lauesen Soren. User Interface Design: A Software Engineering Perspective. Addison Wesley, Pearson Education Limited, Hisashi Kobayashi, Brian L. Mark. System Modeling and Analysis: Foundations of System Performance Evaluation. Prentice Hall, Booch G., Jacobson I., Rumbaugh J. The Unified Modeling Language User Guide. Addison Wesley, Perry William E.Effective Methods for Software Testing. John Wiley & Sons, 3rd edition, O Connor J., McDermott I. The Art of Systems Thinking : Essential Skills for Creativity and Problem Solving. Premium Source Publ., Flood R.L., Carson E.R. Dealing with Complexity. An Introduction to the Theory and Application of Systems Science, 2nd ed. Plenum Press, NY, Google Books. Ackoff R.L. Re-creating the Corporation. The Design of Organizations for the 21 st Century. Oxford University Press, Google Books.

6 McConnell Steve. A Practical Handbook of Software Construction. Microsoft Press, 2nd edition, Pressman Roger. Software Engineering: A Practitioner's Approach. McGraw-Hill Science/Engineering/Math, 7 edition, Hutcheson Marnie L. Software Testing Fundamentals: Methods and Metrics Boehm Barry W. Software Risk Management. New York, NY: IEEE Press, Capers Jones. Assessment and Control of Software Risks. Englewood, NJ: Prentice-Hall, Carr Nicholas G. IT Doesn t Matter. Harvard Business Review, Enhancing Shareholder Wealth by Better Managing Business Risk, IFAC, Abbott Martin L., Fisher Michael T. The Art of Scalability: Scalable Web Architecture, Processes, and Organizations for the Modern Enterprise. Addison-Wesley Professional, White Brain A. Software configuration management strategies and rational clear case Jacobson Ivar. Software Reuse: Architecture, Process and Organization for Business Success. Addison-Wesley Professional, Heldman K. Project Manager's Spotlight on Risk Management Internet-based Publications: Ian Sommerville s web page with available training materials: Software Engineering Conference (Russia) 2005, 2006, Principia Cybernetica Project (PCP), 2002, (in particular, section on Systems Concepts) - ; The Microsoft.NET platform: The Microsoft Solution Framework methodology: Fowler M. Patterns of Enterprise Application Architecture. Addison-Wesley, Dempsey Jed, Dvorak Robert E. and others. A Hard and Soft Look at IT Investments, Other Recommended Sources of Information, including Ones under Free Electronic Access: Miller J.H., Page S.E. Сomplex Adaptive Systems. An Introduction to Computational Models of Social Life, Princeton University Press, Casti J.L. Connectivity, Complexity and Catastrophe in Large-Scale Systems (International Series on Applied Systems Analysis), John Wiley & Sons, COBIT 3rd Edition, Released by the COBIT Steering Committee and the IT Governance Institute, July Casti J.L. Polyhedral Dynamics - II: Geometrical Structure as a Basis for Decision Making in Complex Systems, IIASA Research Memorandum RM , Casti J.L., Karlqvist A. Complexity, Language, and Life: Mathematical Approaches, Springer-Verlag (Heidelberg), Atkin R., Casti J.L. Polyhedral Dynamics and the Geometry of Systems, IIASA Research Report RR , Pidwirny M. Definitions of Systems and Models, Fundamentals of Physical Geography, 2nd Edition, 2006.

7 Ramage M., Shipp K. Systems Thinkers, Springer (The Open University), Google Books. Jackson M.C. Systems Methodology for the Management Sci. Plenum, Google Books. Gharajedaqhi J. Systems Thinking : Managing Chaos and Complexity. A Platform for Designing Business Architecture, 2nd ed. Butterworth-Heinemann Publ., IV. Education control forms / Assessments: - [A] progress (interim) check: end-of-module test (MT) at the end of 1st module, - [B] concluding check: final exam (FE) at the end of 2nd module (the last module of the course) - [C] home assignment (H) during 1 st and 2 nd modules [Assessment] Progress (interim) [A] and concluding check [B] grades are made up of the following components: Work activity (WA) during seminar hours in 1st, 2nd modules is controlled by the use of keeping students attendance records and scoring (evaluation) involvement into discussions as well as quality of exercise performance during seminars. End-of-module test (MT) at the end of module implies arrangement of the written test (in lecture room) for all students enrolled to the course (the possibility of complementary interview with students is still reserved for the purpose of accurate grade confirmation). Subject area covered by the test embraces those topics of the course, which are discussed in both lectures and seminars till the announced date; if student misses the end-of module test because of some valid reason, the grade «absence» is written down to corresponding column of the mark sheet. Depending on the number and complexity of the end-of-module test tasks (final decision is taken by the course instructor), the duration of the test amounts for 90 to 105 minutes. The end-of-module test (MT) is assessed on usual ten-point scale Ultimate grades of the end-of-module check (MT) and concluding check (FE) on ten-point scale are obtained as follows: - (А) grade of the end-of-module check Ultimate MT (at the end of the 1 st module) is calculated as a weighted sum Ultimate MT = 0.2*WA * MT, where WA and MT are ten-point scale grades for the written test (end of the 1st beginning of the 2nd module). Calculated value obtained is rounded to integer grade. Student gets the grade «pass», if Ultimate MT >= 4 (refer to correspondence table below), - (B) concluding check grade (FE) at the end of the last 2 nd module accumulates course results as follows: FE = 0.2*WA+ 0.2*H + 0.6* E, where Work Activities (WA), Home Assignment (H) and Exam (E) are ten-point scale grades. As always, calculated value of FE is rounded to integer grade. Conversion of the concluding rounded grade (FE) to five-point scale grade is done in accordance with the following table: Summary Table: Correspondence of ten-point to five-point system s marks Ten-point scale [10] Five-point scale [5]

8 1 - unsatisfactory 2 - very bad 3 - bad 4 satisfactory 5 - quite satisfactory 6 - good 7 - very good 8 - nearly excellent 9 - excellent 10 - brilliantly Unsatisfactory- 2 Satisfactory- 3 Good - 4 Excellent- 5 V. Course Contents Topic 1. Software engineering fundamentals Introduction to the Software engineering course. Definition of the key questions about software engineering; Organizations, people and computer systems. Explanation the difference between software engineering and computer science; Software costs structure and software engineering methods introduction; Introduction of the ethical and professional issues that concern software engineers. Software engineering main tools and techniques observation Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., [ * original - in Russian] В.В. Липаев Программная инженерия. Методологические основы. Учебник. М.: ТЕИС, Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) TECHNICAL REPORT ISO/IEC TR IEEE First edition ; Carlo Ghezzi, Mehdi Jazayeri and Dino Mandrioli, Fundamentals of Software Engineering (2nd Edition), 2002 Ian Sommerville s web page with available training materials: Roger Pressman, Software Engineering: A Practitioner's Approach. McGraw-Hill Science/Engineering/Math; 7 edition (January 20, 2009); Ackoff R.L. Re-creating the Corporation. The Design of Organizations for the 21 st Century, Oxford University Press, Google Books; Steve McConnell, A Practical Handbook of Software Construction. Microsoft Press; 2nd edition (June 9, 2004). Topic 2. Software process models Introduction of a software process models. Generic process models and when they may be used;

9 Process main activities for requirements engineering, software development, testing and evolution; Process iteration: incremental delivery and spiral development. Advantages and risks. The Rational Unified Process model introduction; CASE technology for software process activities; Summary of software process models: benefits and risks of each key process model. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; CMMI for Development, Version 1.2, CMU/SEI-2006-TR-008 ESC-TR ; David G. Ullman, Mechanical Design Failure Analysis: With Failure Analysis System Software (Mechanical Engineering), 2008; Tom Gilb, Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Elsevier Butterworth-Heinemann, 2006; Ian Sommerville s web page with available training materials: Carlo Ghezzi, Mehdi Jazayeri and Dino Mandrioli, Fundamentals of Software Engineering (2nd Edition), 2002; Topic 3. Project management activities The main tasks undertaken by project managers, roles and responsibilities in managing software development process; The planning process and the project planning activities. Graphical schedule representations; Project staffing and scheduling process definition. Project costing; Project monitoring and reviews. Report writing and presentations; Critical system definition and key properties (system dependability, availability, reliability, safety, security) ; Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; O Connor J., McDermott I. The Art of Systems Thinking : Essential Skills for Creativity and Problem Solving, Premium Source Publ., 2006; Flood R.L., Carson E.R. Dealing with Complexity. An Introduction to the Theory and Application of Systems Science, 2nd ed., Plenum Press, NY, Google Books; Ackoff R.L. Re-creating the Corporation. The Design of Organizations for the 21 st Century, Oxford University Press, Google Books; Ian Sommerville s web page with available training materials: Steve McConnell, A Practical Handbook of Software Construction. Microsoft Press; 2nd edition (June 9, 2004). Topic 4. Software Requirements Definition of a requirement; Different types of requirments:

10 o Concepts of user and system requirements; o Functional and non-functional requirements; o User and system requirements; The software requirements document; Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp.; Course «Applied Systems Analysis» outline: prepared in September-October 2010 [ academic year ] --- page 8; Casti J.L. Connectivity, Complexity and Catastrophe in Large-Scale Systems (International Series on Applied Systems Analysis), John Wiley & Sons, 1979; Casti J.L. Polyhedral Dynamics - II: Geometrical Structure as a Basis for Decision Making in Complex Systems, IIASA Research Memorandum RM , 1975; Ian Sommerville s web page with available training materials: Casti J.L., Karlqvist A. Complexity, Language, and Life: Mathematical Approaches, Springer-Verlag (Heidelberg), Topic 5. Requirements engineering processes Requirements engineering processes activities and their relationships; How to conduct feasibility studies and how to measure the results; Techniques for requirements elicitation and analysis; Requirements validation and the role of requirements reviews; The role of requirements management in support of other requirements engineering processes; Problems of requirements analysis and requirements change management. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; Michael E. Bernstein, Eric J. Braude, Software Engineering: Modern Approaches. Wiley; 2 edition, 2010; Carlo Ghezzi, Mehdi Jazayeri and Dino Mandrioli, Fundamentals of Software Engineering (2nd Edition), 2002; Shari Lawrence Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice (4th Edition), Prentice Hall, 2009; Hisashi Kobayashi, Brian L. Mark, System Modeling and Analysis: Foundations of System Performance Evaluation, Prentice Hall, Ian Sommerville s web page with available training materials: Myer Kutz, Eshbach's Handbook of Engineering Fundamentals Soren Lauesen, User Interface Design: A Software Engineering Perspective. Addison Wesley, Pearson Education Limited, Topic 6. System models and architecture Model types observation: behavioural modelling, data modelling and object modelling;

11 Unified Modelling Language (UML) and CASE workbenches for system modelling; Specification in the software process: formal, sub-system, behavioural specification; Introduction to system architecture; Architectural design process and its importance: o Distributed systems, application and object architecture o Multiprocessor architectures o Client-server architectures Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; Fowler M. Patterns of Enterprise Application Architecture. Addison-Wesley, 2003: Shari Lawrence Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice (4th Edition), Prentice Hall, 2009; Ian Sommerville s web page with available training materials: Strachey C. Fundamental Concepts in Programming Languages. Higher-Order and Symbolic Computation, Vol. 13, No 1/2, April 2000, p Topic 7. System design Definition of a system design process; Introduction in to design process activities; Design process models: object-oriented design, real-time design, interface design, etc.; UML design process brief introduction; System design evolution and development. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; Soren Lauesen, User Interface Design: A Software Engineering Perspective. Addison Wesley, Pearson Education Limited, 2005; Martin L. Abbott; Michael T. Fisher, The Art of Scalability: Scalable Web Architecture, Processes, and Organizations for the Modern Enterprise, Addison-Wesley Professional, 2009 Michael E. Bernstein, Eric J. Braude, Software Engineering: Modern Approaches. Wiley; 2 edition, 2010; Booch G., Jacobson I., Rumbaugh J. The Unified Modeling Language User Guide. Addison Wesley, 1998; Ackoff R.L. Re-creating the Corporation. The Design of Organizations for the 21 st Century, Oxford University Press, Google Books. Ian Sommerville s web page with available training materials: Myer Kutz, Eshbach's Handbook of Engineering Fundamentals. 2009; Soren Lauesen, User Interface Design: A Software Engineering Perspective. Addison Wesley, Pearson Education Limited, Topic 8. Software development Introduction to a software development process;

12 Iterative and incremental development key features; Software development methods overview: o Agile development methods o Principles and practices of extreme programming o Rapid application development Documenting of software development process, system development planning and reporting; Roles of prototyping in the software process. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp.; Myer Kutz, Eshbach's Handbook of Engineering Fundamentals. 2009; Ackoff R.L. Re-creating the Corporation. The Design of Organizations for the 21 st Century, Oxford University Press, Google Books; Roger Pressman, Software Engineering: A Practitioner's Approach. McGraw-Hill Science/Engineering/Math; 7 edition (January 20, 2009). Ian Sommerville s web page with available training materials: Soren Lauesen, User Interface Design: A Software Engineering Perspective. Addison Wesley, Pearson Education Limited, Topic 9. Software reuse and evolution Software evolution processes and ways of software reuse implementation; Benefits of software reuse and some reuse problems; Development of software product lines; Software maintenance and maintenance cost factors; Program evolution processes and dynamics. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp.; Roger Pressman, Software Engineering: A Practitioner's Approach. McGraw-Hill Science/Engineering/Math; 7 edition (January 20, 2009); Software Engineering Inst. Carnegie Mellon Univ. The Capability Maturity Model: Guidelines for Improving the Software Process. SEI, 2008; Ivar Jacobson, Software Reuse: Architecture, Process and Organization for Business Success, Addison-Wesley Professional, 1997; Soren Lauesen, User Interface Design: A Software Engineering Perspective. Addison Wesley, Pearson Education Limited, Ian Sommerville s web page with available training materials: Michael E. Bernstein, Eric J. Braude, Software Engineering: Modern Approaches. Wiley; 2 edition, Topic 10. Verification and validation Verification and validation process, what s the difference; Program inspection process, planning of software inspections; Verification and formal methods;

13 Critical Systems Validation: reliability validation, safety assurance, security assessment; Key principles of automated static analysis; Cleanroom software development process. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) TECHNICAL REPORT ISO/IEC TR IEEE First edition ; CMMI for Development, Version 1.2, CMU/SEI-2006-TR-008 ESC-TR ; David G. Ullman, Mechanical Design Failure Analysis: With Failure Analysis System Software (Mechanical Engineering), 2008; Tom Gilb, Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Elsevier Butterworth-Heinemann, Software Engineering Inst. Carnegie Mellon Univ. The Capability Maturity Model: Guidelines for Improving the Software Process. SEI, Topic 11. Software Testing Software testing guidelines and main tools and techniques; Main principles of system and component testing, validation testing and defect testing; Strategies for generating system test cases, test case design; Essential characteristics of tool used for test automation; The results of software testing, how to measure test results. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; Marnie L. Hutcheson, Software Testing Fundamentals: Methods and Metrics. 2003; William E. Perry, Effective Methods for Software Testing. John Wiley & Sons; 3rd edition (26 Oct 1995) ; Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) TECHNICAL REPORT ISO/IEC TR IEEE First edition Rex Black, Managing the Testing Process. Microsoft Press,U.S.; Pap/Cdr edition (1 Jun 1999). Carlo Ghezzi, Mehdi Jazayeri and Dino Mandrioli, Fundamentals of Software Engineering (2nd Edition), Topic 12. Managing People and cost estimation Staffing principles: selecting and retaining staff; Factors that influence individual motivation; Key issues of team working including composition, cohesiveness and communications; The people capability maturity model (P-CMM); Software cost estimation techniques, algorithmic cost modeling. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp.; Software Engineering Inst. Carnegie Mellon Univ. The Capability Maturity Model: Guidelines for Improving the Software Process. SEI, 2008 Jackson M.C. Systems;

14 Methodology for the Management Sci., Plenum, Google Books; O Connor J., McDermott I. The Art of Systems Thinking : Essential Skills for Creativity and Problem Solving, Premium Source Publ., Flood R.L., Carson E.R. Dealing with Complexity. An Introduction to the Theory and Application of Systems Science, 2nd ed., Plenum Press, NY, Google Books; Ackoff R.L. Re-creating the Corporation. The Design of Organizations for the 21 st Century, Oxford University Press, Google Books. Topic 13. Software risk management The risk management process and objectives; Main tasks undertaken by risk managers; Risk management planning and the planning process; Risk identification tools and techniques; Risk analysis: qualitative and quantitive analysis; Risk monitoring and control. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; Barry W. Boehm. Software Risk Management. New York, NY: IEEE Press, 1989; Capers Jones, Assessment and Control of Software Risks. Englewood, NJ: Prentice-Hall, 1994; Carr, Nicholas G., IT Doesn t Matter, Harvard Business Review, May 2003; Enhancing Shareholder Wealth by Better Managing Business Risk, IFAC, 1999; Heldman K. Project Manager's Spotlight on Risk Management, Dempsey Jed, Dvorak Robert E. and others. A Hard and Soft Look at IT Investments, COBIT 3rd Edition, Released by the COBIT Steering Committee and the IT Governance Institute, July Topic 14. Quality management and process improvement Quality management process and key quality management activities; Process and product quality, the role of standards in quality management; Software metrics (predictor metrics and control metrics), limitations of software measurement; Quality assurance and standards: o Quality planning o Quality monitoring and control Process and product quality improvement. CMMI process improvement framework. Sommerville I. Software Engineering (8th Edition). Pearson Education Ltd., 2008, 850 pp. ; John Bird, Engineering Mathematics Pocket Book. Newnes, 2008; Software Engineering Inst. Carnegie Mellon Univ. The Capability Maturity Model: Guidelines for Improving the Software Process. SEI, 2008; Michael E. Bernstein, Eric J. Braude, Software Engineering: Modern Approaches. Wiley; 2 edition, 2010.

15 Carlo Ghezzi, Mehdi Jazayeri and Dino Mandrioli, Fundamentals of Software Engineering (2nd Edition), 2002; Shari Lawrence Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice (4th Edition), Prentice Hall, Topic 15. Configuration management Software configuration management process; Configuration management planning, change management, version management and system building; CASE tools to support configuration management processes; Configuration management documenting and measuring. Software Engineering Guide to the Software Engineering Body of Knowledge (SWEBOK) TECHNICAL REPORT ISO/IEC TR IEEE First edition ; Steve McConnell, A Practical Handbook of Software Construction. Microsoft Press; 2nd edition (June 9, 2004) ; Brain A.White, Software configuration management strategies and rational clear case, 2005 Roger Pressman, Software Engineering: A Practitioner's Approach. McGraw-Hill Science/Engineering/Math; 7 edition (January 20, 2009). Ian Sommerville s web page with available training materials: Flood R.L., Carson E.R. Dealing with Complexity. An Introduction to the Theory and Application of Systems Science, 2nd ed., Plenum Press, NY, Google Books. VI. Assignment topics for various education control forms: Home assignment is made as a paper essay on one of the following topics: Describe s software process model (of your choice); Describe a methodology of development (of your choice); Technologies of Agile software development; Web-based software development and information systems; Innovative models and tools for software development; Technologies for client-server systems development; Describe use case modeling, apply use case to a software development; Conduct analysis of a various testing methods to a specific system development (of your choice) and choose the most effective method for software testing; Technologies and tools for ERP system development with description of high-level architecture and configuration; Conduct overview and analysis of the development methodology, analyze benefits and negative factors of each applying to the specific system development case; Describe specifics of RAD technology. What is the mail difference from the other development techniques? CASE modeling features for software development;

16 Features of distributed software engineering (of your choice); ISO 9001 and quality management in software engineering; Conduct CMMI assessment according to CMMI process model (industry, system, process of your choice); Describe any testing methodology (for your choice); Conduct risk assessment using specific risk management identification and assessment techniques (industry, system, process of your choice); Apply quality management assessment to software development process in accordance to international quality standards; Conduct post implementation audit and analyze implementation results. VII. Topics for course results quality assessment Exemplary questions: What are the fundamental ideas of software engineering; Give a definition of terms «system engineering», «software engineering», «subsystem», «software process», «web-based systems», etc. (the matter is related to main concepts introduced in the training course); Provide examples of different application types and give its mail characteristics? What is the difference between software engineering and computer science? What is the difference between software engineering and system engineering? What are the incremental development problems and benefits? What is a software process model? Provide examples? Describe different types of system and their requirements to appropriate software engineering tools and techniques for the development? What are the key challenges facing software engineering? Provide examples and give short explanations? What is meant by verification and validation? What is the difference between verification and validation? What includes system testing? Describe V-model? What types of testing do you know? Provide examples? What are the costs of software engineering? Describe software design process and provide examples of different types of software design? Requirements engineering. Types of requirement, requirements completeness and consistency? What are the best software engineering techniques and methods? Rapid software development and delivery. Problems and benefits? What differences has the web made to software engineering? Illustrate your answer (and explanations) by example related? Describe essential attributes of good software (product characteristic) What are the main software process activities? What is the need of software prototyping? Where it can be used? What are the benefits and problems of prototyping? Software reuse and maintenance. Problems and benefits. Provide examples and give short explanations?

17 What is the purpose of project management in software engineering? Describe the mail areas to be managed? Quality management and software standards. Provide examples of software measurement and metrics according to ISO 9001 standards? The CMMI process improvement framework. Process areas in the CMMI? The author of the program: Dmitry Alexandrov