Software Context and Methology Revision

Pregunta	Respuesta
Spiral	Guides a team to adopt elements of one or more process models. Each phase starts with a design goal and ends with the client reviewing the process.
Spiral - Enginerring	Insert
Spiral - Planning	Estimates cost, schedule and resource for the iteration. Understanding the requirements for continuous communication between the system analyst and the customer
Spiral - Risk analysis	Identification of potential risks are done, risk mitigation strategy is planned and finished
Spiral - Transition	Evaluation of software by customer
Spiral advantages	Good for complex customer requirements Additional functionality or changes can be done at a later stage
Spiral disadvantages	Needs to be strictly followed Risk of not meeting budget or schedule
Agile	Iterative approach. Compromises various approaches under which requirements and solutions evolve through collaborative efforts.
Agile advantages	Clients are involved in every stage Focus on people and process' Very flexible due to iteration
Agile Disadvtages	Can be excessive preparation and planning Lack of test automation
Waterfall	Project activities are in linear sequential phases, where each phase depends on the outcome of the previous one. It is less iterative and flexible, as progress flows in one direction
Waterfall advantages	Easy to manage Fast delivert
Waterfall Disadvantages	Doesn't support changes Difficult to revert back to a previous phase
V-Model - Verification Phase	Insert
Lean	- Focus on the customers - Energise the team - Eliminate waste - Learn quickly - Keep improving
Technical Architect	Defines the structure of a program of system. They can act as a project manager overseeing IT assignments that are aimed at improving the business and ensuring all parts of the project runs
V-Model Advantages	1. Simple and Easy to understand 2. Highly disciplined model
System testing is	Checks system functionality and communication with other systems
Developers	Creates code and does the initial testing. They work closely with the analysts and the designers.
Big Bang Advantages	1. Easy to manage 2. Little resources required
User stories	Special product backlog systems that describe a feature, says how it behaves and what is happening for the user
Coach	Helps the team by trying to avoid making previously made mistakes
Scrum master responsibilities	1. Help the development team achieve their goals 2. Remove impediments from the team 3. Shield the team from interruptions during the sprint
SDLC order	1. Feasibility study 2. Requirements analysis 3. Design 4. Code development 5. Testing 6. Deployment 7. Maintenance
XP Developer	Responsible for releasing stories identified by the customer
Lean Principles	- Eliminate waste - Amplifying learning - Decide as late as possible - Delivery as fast as possible - Empower the team
V-Model Disavantages	Difficult to add or change functionality once project has reached testing No working software until late into the life cycle
Role of the customer	Uses the system in their work. Defines requirements, Reviews specifications, Work with the developers to introduce the system, Conducts acceptance tests
Unified Process (UP)	An iterative and incremental software development process framework Each iteration is like a small project and with each iteration, new features arrive
SDLC is independent of software development methodology used? T/F?	True
Objectives of maintenance stage	Adapt and modify software as users' needs change through time after deployment Fix bugs found during live operation of software
When in the SDLC is it important to involve security domain experts?	Design Testing
Name 2 iterative methodologies	Agile Spiral
Name () incremental methodologies	Waterfall
What is lean?	Offers a solid conceptual framework, values, principles and good practice.
XP disadvantages	Code is more of a focus than design Lack of documentation
Software development teams should adopt a structure that is appropriate for their organisation irrespective of whether project working used	True Project working??
Why should you apply traceability and cross-referencing between software development deliverables and requirements?	To ensure requirements have been met, and identify ones which havent.
Kanban advantages	Easy to manage due to rigidity of the model Accurately models how work is done
XP values	Respect Courage Feedback Communication Simplicity
Requirements analysis	Breaks down system to analyse the situation project goals in an attempt to engage users so that definite requirements can be made
UP - Transition Stage	System is deployed Feedback is received and results in refinements over several transition periods Incorporates user training and system conversions
XP advantages	Encourages teamwork Uses continuous testing
UP advantages	Adaptable to changing requirements Predictable
Role of domain experts	Knowledge in domain other than software. Often asked to review, improve and approve technical work
Product backlog	Ordered list of all the items a team may work on with the highest priority item on top. The product owner should maintain the backlog
Lean advantages	Eliminates unnecessary activity Streamlines approach allows more functionality to be delivered in less time
Acceptance Testing	Tests in the user environment where it can uncover compatibility issues and check non-functioning requirements
Big bang disadvantages	Can be expensive Not good for complex / OOP projects
What is the V-Model	An extension of waterfall and is based on each association of testing phase for each corresponding development stage. The next phase start when the previous one ends.
Feasibility Study	Considering potential risks of developing software Determining whether the project outcome will be worth the costs involved
Role of the designer	Designs solutions to business problems based on requirements specification provided. This includes software design, database design, and UI design
Kanban disadvantages	If Kanban board becomes outdates, it becomes over complicated Poor model for long projects
Business Analyst	Define and refine features in conjunction with a technical lead. They also organise the requirements
The tracker	Keeps track of relevant metrics and identifies areas for improvement
Use of V-Model in SDLC	Each stage of the SDLC has a corresponding verification and validation stage
Big Bang	Model for projects with no end date and unsure requirements. All resources go on the software development and code. Small projects, small teams
What is produced in the design stage	Software specification
Role of SCRUM development team	Commits to finishing sprints and are flexible in what they contribute to the sprint. Goals are the most important and all team members should be able to perform the task.
In which stage are interaction diagrams a deliverable?	Design
Unit testing	Tests individual modules for bugs
Kanban	Emphasis on continual delivery while not overburdening the development team. Helps teams work together more efficiently. (Production line)
Project manager	Leads and motivates the team. They also track the development progress and are the link between the development team and the customer
Testers	Responsible for creating test plans. Doing black/white box testing. Documenting test results that inform developers of bugs to fix.
Purpose of the SDLC	To provide a set of steps to create a software end-product
Which method allows software to be deployed for client use after each iteration?	Agile
Domain Expert	Provide insight into business products and processes
Responsibilities of product owner in agile method	Prioritising items on the backlog Accepting stories as done Representing the customer to the Agile team
Feasibility study	Determining the costs, benefits, resource requirements and user needs required for completion
Lean disadvantages	Needs skilled team Depends on strong documentation sippin lean ayyy
Design	Turn specification into design plan All stakeholders review plan and feedback Output of this stage describes the system as a collection of modules
UP Disadvantages	Development process is complex and disorganised
UP - Inception stage	Develops an approximate vision of the system, makes a business case and produces a rough estimate for the cost and schedule
Maintain	The software is improved and can be updated to fit new requirements
Test	Tests for defects against the specification so bugs and defects are detected and removed. This includes unit, system and user acceptance testing.
Development	Building the software, distribution, installing the software, configuring the software and testing the software.
Sponsor	Monitor the project from a business standpoint and let the higher ups know about progress
UP - Elaboration stage	Team should: Capture the system requirements. Know the risk factors. Establish and validate the system architecture. Create design,
Integration testing	Tests coexistence and communication between modules
V Model - Coding	Coding the modules, code reviews and cost optimisation happens. At the end the code is put in the repository.
Kanban values	Transparency Balance Collaboration Customer focus Flow leadership Understanding Agreement & Respect
Black box testing	The tester cannot see the code. They are aware of what the code should do but not how it is done
UP - Construction Stage	System is built on the foundations laid in the elaboration stage. User cases are created and each one signifies a new iteration. Each iteration results in a release of the software.
Scrum Events	Daily start-up meetings Sprint planning and reviews
V Model - Validation Phase	The testing phase. This includes user testing, integration testing, system testing and acceptance testing
Product Owner	Voice of the customer. Determines what the team works on based on priority. Stake holders communicate with the product owner.
Deployment	Delivers software to end users, more adjustments can be made. Involves giving operators training. System is placed in its final environment
In what scenario would you potentially use agile?	The customer has very few formally documented requirements.
What is provided by a "Change history" table	An audit trail of the reasons for change. Providing information for stakeholders. (this question isn't great)
Scrum - Sprint	A basic unit of work Can be various length and is started when the old sprint ends
System Analyst	Analyses and plans the flow of data in a system, and looks at existing solutions. Writes technical requirements of the system and talks to designers about ideas

Siguiente

Software Context and Methology Revision

Descripción

Resumen del Recurso

Similar

	Creado por Tyler Huxley-Wright hace más de 3 años