GoConqr has a new look! Let us know what you think.

Sign up free

Flashcards

G51FSE - Software Engineering

Michael Mee English 43 cards

Cards in this deck (43)

  1. 1What are the four fundamental stages of software development?Specification, Design, Validation, Maintenance
  2. 2Explain the difference between project risks and software risks.Software risks are problems that can occur as a result of issues in the software, whereas project risks are problems that can impact the development of the software
  3. 3Why were formal software engineering were losing favour in the 90s?The available models were all slow and expensive, depends on a lot of documentation and it was difficult to manage changes in projects.
  4. 4What are the four original values of the Agile manifesto?Prioritize individuals and interactions over processes and tools, working software over documentation, customer collaboration over contract negotiation and responding to change over following a plan.
  5. 5How does Extreme Programming (XP) work?Identify user stories for each release, breaking them into tasks. Plan the release and develop over a short period (1-2 weeks), testing using an automated test framework. Meet with customer at the end of period to evaluate.
  6. 6How does Extreme Programming utilise continuous integration?As soon as work on a task is complete, it is integrated into the whole system. All unit tests must pass in the system.
  7. 7How is paired programming integrated into Extreme Programming?Developers work in pairs, checking each other's work. They work on all areas of the system so that no islands of expertise develop and all developers take responsibility.
  8. 8How does Extreme Programming meet Agile values?Full-time customer engagement gives customer collaboration. Small frequent system releases creates working software. Pair programming, collective ownership and sustainable working hours supports individuals and interactions. Responds to change with regular system releases.
  9. 9What is the main aim of Extreme Programming?Team effectiveness.
  10. 10What is the main aim of Scrum?Optimising time and delivery.
  11. 11What is the main aim of Kanban?Optimising speed of feature delivery.
  12. 12How does Scrum work?Plan and outline what you will achieve, set a series of sprint cycles doing the work and then document the current phase.
  13. 13What is meant by a Scrum sprint cycle?A period of 2-4 weeks to achieve the current plan, acting as intermittent points to what shall be achieved by the next point, involving continuous group communication.
  14. 14How does Kanban work?A Kanban board is used to manage current work, driven by an updating priority list containing features to be built - when one is completed, it is integrated and released, then the next one is picked.
  15. 15How is time taken to build features measured in Kanban?Release cycles.
  16. 16What are Agile methodologies especially good for?Small/medium sized projects that have an involved customer.
  17. 17What are some difficulties of getting Agile methods to be impactful?Not always easy to have an involved customer long term, harder to plan and budget, team members may have wrong personalities, and can be seen a risk by companies.
  18. 18If a project needs a very detailed specification and design before implementation - plan or agile?Plan.
  19. 19If it is realistic that a project can deliver software to customers and get rapid feedback from them - plan or agile?Agile.
  20. 20If the project requires careful analysis before implementation - plan or agile?Plan.
  21. 21If the project needs to be revised or updated regularly needing documentation - plan or agile?Plan.
  22. 22If the tools you are using for a project are good at keeping track of change - plan or agile?Agile.
  23. 23If a project needs clear documentation to communicate between project partners?Plan.
  24. 24If the team working on the project has all the right requirements, design, testing and skill-sets - plan or agile?Agile.
  25. 25If the project is safety critical or subject to external regulation - plan or agile?Plan.
  26. 26What does software quality mean?Doing every aspect well - acceptance testing, unit testing and coding.
  27. 27What are quality assurance teams responsible for?Planning for quality, defining standards and procedures for the whole company and checking that projects conform to those standards.
  28. 28What is the quality assurance process?Checks the project deliverables to ensure that they are consistent with organisational standards and goals.
  29. 29What is a project quality plan?A plan that sets the bar for the team to achieve, describing product plans, description of the process, quality goals and expected key risk areas/management.
  30. 30What are the aims of planning for quality?To identify standards that will be met, recommending quality-promoting processes for the project, showing what will count as good quality.
  31. 31What are product standards?Standards for documentation, coding conventions, class structure, etc...
  32. 32What are process standards?Standards for when testing is done, defining good practices at each stage of the SE process.
  33. 33What are ISO standards?Existing standards - ISO 9000 provides standards on quality management processes and ISO 9241 provides standards on accessibility factors.
  34. 34How are traditional inspections carried out?A group of 3-7 people examine an output from a SE process, involving QA team reviewers, project manager, senior designers and those who led the process.
  35. 35What are traditional inspections used to find?Problems and non-conformance to standards, checking for completeness, missing or incorrect logical steps, nonsensical segments of the project.
  36. 36What are Fagan inspections?Inspections specialised for inspecting code with more specific roles - moderator, designer, coder and tester.
  37. 37What is the general software review process?People independently examine any documentation in advance, then a person reads through and the group attempts to find - not fix - problems. The output is a list of problems to be fixed.
  38. 38What are common inspection problems?Unprepared participants, participants worrying their performance will be judged, criticizing those who made the document instead of discussing how to make it better.
  39. 39What are control/process measures?The measuring of the success of your SE process, helping to decide whether to improve processes later.
  40. 40What are code/predictor measures?Measures to help predict aspects of code quality, but are only predictors.
  41. 41What are steps you can take to deal with potential risks?Hazard avoidance, hazard detection + removal and damage reduction.
  42. 42What are the methods you can take towards dealing with risks?Avoidance and minimisation strategies, with contingency plans if the risk occurs.
  43. 43—

Information

Description
Flashcards on G51FSE - Software Engineering, created by Michael Mee on 17/05/2019.
Created by
Michael Mee
Views
1
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?