Software Engineering

Ch2 Slide 7: 'The waterfall model — Plan-driven model. Separate and distinct phases of specification and development. Incremental development — Specification, development and validation are interleaved... Integration and configuration — The system is assembled from existing configurable components.'

Ch3 Slide 5 (Agile manifesto): 'Individuals and interactions over processes / Tools over comprehensive documentation / Customer collaboration over contract negotiation / Responding to change over following a plan.'

Ch3 Slide 35: 'Sprints are fixed length, normally 2–4 weeks. The starting point for planning is the product backlog... selection phase involves all of the project team who work with the customer to select the features...'

Ch3 Slide 14 (Influential XP practices): 'User stories for specification / Refactoring / Test-first development / Pair programming.'

Ch8 Slide 23 (Automated testing): 'In automated unit testing, you make use of a test automation framework (such as JUnit) to write and run your program tests.' Ch3 Slide 22: 'Usually relies on a testing framework such as Junit.'

Ch4 Slide 28: 'a number of generic activities common to all processes — Requirements elicitation; Requirements analysis; Requirements validation; Requirements management.'

Ch4 Slide 25 (Usability requirements example): 'Medical staff shall be able to use all the system functions after four hours of training. After this training, the average number of errors made by experienced users shall not exceed two per hour of system use. (Testable non-functional requirement)'

Ch4 Slide 45: 'Scenarios and user stories are real-life examples of how a system can be used. Stories and scenarios are a description of how a system may be used for a particular task.'

Ch4 Slide 41 (Ethnography): 'A social scientist spends a considerable time observing and analysing how people actually work.'

Ch5 Slide 6 (UML diagram types): 'Activity diagrams... Use case diagrams... Sequence diagrams... Class diagrams, which show the object classes in the system and the associations between these classes. State diagrams...'

Ch5 Slide 50 (Types of model): 'A computation independent model (CIM)... A platform independent model (PIM)... Platform specific models (PSM).'

Ch6 Slide 23: 'The Model-View-Controller (MVC) pattern.' Ch6 Slide 33: 'Client-server architecture / Distributed system model which shows how data and processing is distributed across a range of components.' Ch6 Slide 36: 'Pipe and filter architecture.'

Ch6 Slide 51: 'These systems are often implemented as multi-tier client server/architectures... The web server is responsible for all user communications, with the user interface implemented using a web browser; The application server is responsible for implementing application-specific logic... The database server moves information to and from the database and handles transaction management.'

Ch5 Slide 55 (iLearn service integration): 'Integrated services are services which offer an API (application programming interface) and which can be accessed by other services through that API. Direct service-to-service communication is therefore possible.'

Ch7 Slide 7 (Process stages): 'Define the context and modes of use of the system; Design the system architecture; Identify the principal system objects; Develop design models; Specify object interfaces.'

Ch7 Slide 38 (Design problems): 'Tell several objects that the state of some other object has changed (Observer pattern). Tidy up the interfaces to a number of related objects... (Façade pattern). Provide a standard way of accessing the elements in a collection... (Iterator pattern). Allow for the possibility of extending the functionality of an existing class at run-time (Decorator pattern).'

Ch7 Slide 46 (Configuration management activities): 'Version management, where support is provided to keep track of the different versions of software components. Version management systems include facilities to coordinate development by several programmers. System integration... Problem tracking...'

Ch7 Slide 59 (License models): 'The GNU General Public License (GPL)... The GNU Lesser General Public License (LGPL)... The Berkley Standard Distribution (BSD) License.'

Ch8 Slide 18 (Development testing): 'Unit testing, where individual program units or object classes are tested... Component testing, where several individual units are integrated... System testing, where some or all of the components in a system are integrated...'

Ch8 Slide 27: 'Each of these classes is an equivalence partition or domain where the program behaves in an equivalent way for each class member. Test cases should be chosen from each partition.'

Ch8 Slide 48 (Regression testing): 'Regression testing is testing the system to check that changes have not "broken" previously working code... with automated testing, it is simple and straightforward. All tests are rerun every time a change is made to the program.'

Ch8 Slide 56 (Performance testing): 'Performance tests usually involve planning a series of tests where the load is steadily increased until the system performance becomes unacceptable. Stress testing is a form of performance testing where the system is deliberately overloaded...'

Ch9 Slide 55 (Refactoring): 'Refactoring involves modifying a program to improve its structure, reduce its complexity or make it easier to understand. When you refactor a program, you should not add functionality but rather concentrate on program improvement.'

Ch22 Slide 13 (The risk management process): 'Risk identification — Identify project, product and business risks; Risk analysis — Assess the likelihood and consequences of these risks; Risk planning... Risk monitoring...'

Ch22 Slide 35: 'Task-oriented people, who are motivated by the work they do... Interaction-oriented people, who are motivated by the presence and actions of co-workers. Self-oriented people, who are principally motivated by personal success and recognition.'

Ch23 Slide 30 (Schedule presentation): 'Bar charts are the most commonly used representation for project schedules. They show the schedule as activities or resources against time. Activity networks — Show task dependencies.'

Ch23 Slide 57 (COCOMO 2 models): 'Application composition model... Early design model... Reuse model... Post-architecture model.'

Ch23 Slide 40 (Story-based planning): 'Stories are assigned "effort points" reflecting their size and difficulty of implementation. The number of effort points implemented per day is measured giving an estimate of the team’s "velocity".'

Ch2 Slide 55 (The SEI capability maturity model): 'Initial — Essentially uncontrolled / Repeatable... / Defined... / Managed — Quality management strategies defined and used / Optimising — Process improvement strategies defined and used.'

Ch3 Slide 53 (Scaling up to large systems): 'Continuous integration is practically impossible. However, it is essential to maintain frequent system builds and regular releases of the system.' Ch3 Slide 9 (XP): 'New versions may be built several times per day; Increments are delivered to customers every 2 weeks; All tests must be run for every build and the build is only accepted if tests run successfully.'