Flashcards
1.2.3/2.2.2 Software Development
Cards in this deck (16)
- 1Software development1.2.3 (A2), 2.2.2 (AS)
- 2Brook's law (1975)"too many cooks spoil the broth"
claim about software project management which claims that adding more manpower to a late project makes it later. - 3Feasibility StudyMakes sure the proposed project is legal and that is technically achievable.
Also the project must be financially viable. - 4Requirements specificationVery detailed list of what the new system MUST deliver. Everything must written in a way so that it can be answered with yes or no however the specifications cant be vague in any way.
- 5Good examples of requirements specification.Table will be arranged in 2 rows and 4 columns.
The buttons at the bottom of the screen will allow the user to see previous records, save the record or see the next record IN THAT ORDER. - 6Bad examples of requirements specification.The table should hold data.
There will be buttons to enable the most important record functions. - 7Uses of requirements specification.Producing the specification of the system/programs and for testing of the completed system.
Therefore the user needs to sign that the requirements are correct at the beginning of development and that the system is accepted as delivering these specs. - 8DocumentationA range of documents produced during system development.
Requirements specification
System design (algorithms, GUI layouts data storage designs)
technical documentation (descriptions of code. Normally automatically produced by built in software development tools.)
User documentation (help guide for people using system) - 9Software development methodologiesUsed to meet standards of software development and implementation. Many different types.
- 10Waterfall life cyclesplit into stages - at the end of each stage the process flows onto the next stage
As many stages as is needed - generally restricted to 6 for exams. - 11Benefits and drawbacksOften a good idea to go back and alter previous stages but cant do this during waterfall cycle.
Basically doesnt work.
Very simple.
IF well written everyone involved knows exactly what they are doing - 12Agile methodologiesGroup of methodologies which were developed in the early 2000's and designed to reduce issues that arise in the waterfall cycle by acknowledging users needs that werent addressed or monitored during waterfall cycle
- 13DrawbacksStaffing communication between user and developer are significant. Users are not used to helping developers.
Time commitment for both sides is significant, it needs to be ongoing and it isnt easy to provide a figure at the beginning.
Clients like to know exactly what something will cost and do - This is near impossible with Agile.
Terminology - jargon user may not understand developer/vice versa. - 14BenefitsCommunication is ongoing and detailed so little space for secrecy.
Collaborative efforts between developers and users is essential.
PAYG costing - charged an agreed rate (normally daily) until client agrees the project is complete - 15rapid application development (RAD)Heavily dependent on production of series of prototypes. Prototypes can be used to just develop look and feel however they are quick to develop and essential to getting user agreement about product.
Process of refining prototypes is cyclical: prototype developed, user states what needs to be changed, developer changes it, repeats. - 16Drawbacks0
Information
- Description
- Flashcards on 1.2.3/2.2.2 Software Development, created by Harvmeister on 07/12/2015.
- Created by
- Harvmeister
- Views
- 2
- Rating