1.2.3 Software Development
No description yet. This curated deck is ready for daily study.
Card preview (18)
1.2.3 A) What is the software development life cycle
Analysis Design Development Testing Implementation evaluation maintenance
1.2.3 A) What is the software development life cycle What is the analysis phase
What needs for the stakeholders. Strengths and weaknesses. What data types will be used
1.2.3 A) What is the software development life cycle What is the design phase
Inputs and outputs , security , hardware , UI , testing plan
1.2.3 A) What is the software development life cycle What is the development phase
Split design into self contained modules
1.2.3 A) What is the software development life cycle What is the testing phase
Alpha and beta testing Alpha in house testing beta carried out by end user white and black box testing white box = all possibilities of program are tested (Dry Runs / Trace Tables ) black box = without being aware of internal structure (Tests the expected output based on input)
1.2.3 A) What is the software development life cycle What is the implementation phase
Make changes from testing , publish software
1.2.3 A) What is the software development life cycle What is the evaluation phase
Effectiveness of the software what can be changed
1.2.3 A) What is the software development life cycle What is the maintenance phase
Updates
1.2.3 A) What is the waterfall lifecycle
Complete in sequence Analysis includes feasibility of project using TELOS Technical , Economical , Legal , Operational , Scheduling if changes made all levels must be revisit, users have little input
1.2.3 A) What is the agile methodology
Aims to improve flexibility adapts to changes in user requirement problem broken down into sections which developed in parallel priority on user satisfaction Analyse > design prototype > build prototype > userfeed back > refine prototype > design prototype or > final product.
1.2.3 A) What is extreme programming
An agile methodology in which pairs of programmers alongside a representative end user make a team. Aim to improve quality of code in order to be effective programmers must communicate.
1.2.3 A) What is the spiral model
Four key stages with focus of effectively managing risks large projects. Analyse system requirements > pinpoint and mitigate risks, development , testing evaluation. suitable for large programs and expensive
1.2.3 A) What is rapid application development
Iterative method , partially functioning prototype constantly build up apon. User requirements gathered. user feedback. continued till final product. May be in eff Prototype is created (1) – (Evaluated and) feedback used to inform next iteration (1) – Any changes are made (1) – Process repeated until…(1) …prototype becomes final product. (1)
1.2.3 B) Adv , DAdv , uses of waterfall
A) Straight forward, clearly documented D) Low flexibility , no risk analyse, limited user input U) Low risk projects, general purpose software, large projects
1.2.3 B) Adv , DAdv , uses of Agile
A) High qual code , Flexibility , lots of user input D) low documentation , consistent interaction between programmer and user U) small project with unclear requirements
1.2.3 B) Adv , DAdv , uses of spiral
A) risk analysis , catered for user needs , many prototypes D) Expensive , lack of efficient code U) large code, risk intensive , high budget
1.2.3 B) Adv , DAdv , uses of rapid applications development
A) catered to user , usable , quick development D) low documentation U) small , low budget, small time period
1.2.3 C) writing and following algorithms
inputs clearly defined valid outputs for defined inputs able to deal w/ invalid inputs reaches a stopping conditions well documented well commented