1.2.3 Software Development

A number of distinct phases programmers work through to develop a solution to a problem

-Whether or not the project can be done -five factors must be considered (economic, time, technical, political, legal)

-A requirement is a specific feature of the new system and is recorded in a document called requirements specification

Interface – how the user interacts with it. Functional – what will the system do Performance – how well/fast will the system respond

-the process of taking the requirements of a new system and deciding what the system will look like, how will it store data and how it will process data -Design can only go ahead once the requirements specification has been completed

-waterfall -RAD (rapid application development) -spiral -agile -extreme programming

-Each phase has a well-defined start and end point with identifiable deliverables -evolution of the waterfall model allows you to move backwards or forwards to a different stage as developers often have to rework earlier stages in light of knowledge gained as development progresses

-risk-driven -more of a guide for development teams, decisions on the software development methodology are made based on the risks identified -it is wholly dependant on the project and its unique risks (not fixed)

-that involves producing successive prototypes of the software until a final version is produced and approved -increasingly refined prototypes are made with reduced functionality -These are designed, coded, tested and evaluated with the end user

-The product is built in a series of iterations known as sprints -sprints are short, time-boxed periods when a team has focused goals to complete a set amount of work -Each sprint should ideally be a bite-sized piece of focused work, taking no longer than one to four weeks

-not so much a software methodology as it is a framework -considered an agile framework as it encourages regular, small, iterative software releases ​ -aims to produce very high-quality code and promote developers’ quality of life by encouraging them to adopt a set of common practices that focus on the values of:​ -Simplicity​ -Communication​ -Feedback​ -Courage​ -Respect​

-Identify the problem​ -Assess the feasibility: technical, economic, legal, operational, time​ -Analyse the system​ -Design a solution​ -Code (implementation)​ -Testing​ -Go live: direct changeover, phased, parallel or pilot​ -Evaluation​ -Maintenance: adaptive and corrective​

-Collective code ownership​ -Continuous integration​ -Code standards​ -Refactoring​ -Paired programming​

-Hypertext Markup Language, a standardized system for tagging text files to achieve font, color, graphic, and hyperlink effects on World Wide Web pages -HTML elements consist of start and end tags with content in between

<html> </html> = document begins and ends with <body> </body> = the main test begins <h1> </h1> = this is a heading <p> </p> = defines a paragraph <head> </head> = a container for metadata (data about data) that is place between the <html> and <body> tags

-A sequence of steps designed to perform a task