Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
Software Engineering
Test 2
| Question | Answer |
|---|---|
| Brooks law | Adding additional programming personnel to a team when a product is late has the effect of making the product even later |
| Teams For Agile Processes | All code is written by two programmers sharing a computer "Pair programming" |
| Open-Source Programming Teams | Are generally staffed by teams of unpaid volunteers Who communicate asynchronously (via e-mail) With no team meetings and With no managers There are no specifications or designs little or no other documentation |
| Execution-based testing | Testing through test cases |
| Non-execution-based testing | Testing software without running test cases Examples Reviewing software Walkthroughs Inspections Analyzing software mathematically |
| Managerial Independence | Each group must fall under their own manager Neither manager should be able to overrule the other |
| How to handle conflict of interest (MI) | More senior manager must decide whether to Deliver the product on time but with faults, or Test further and deliver the product late The decision must take into account the interests of the client and the development organization |
| Involved in Walkthrough | A walkthrough team consists of from four to six members It includes at least one representatives from The team responsible for the current workflow The team responsible for the next workflow A client representative The SQA group |
| Participant-driven | Participants present their lists of unclear items and items they think are incorrect Representative of team must respond to each query Clarifying what is unclear to the reviewer agreeing that there is a fault or explaining why the reviewer is mistaken |
| Document-driven | A person responsible for the document walks the reviewers through the document Reviewers interrupt with their prepared comments or comments triggered by the presentation |
| five formal steps of inspection | Overview:Overview of document is given by individuals responsible for document Preparation Participants try to understand document in detail Inspection One participant walks through the document with the inspection team and the fault finding commences |
| five formal steps of inspection (4-5) | Moderator produce a report Rework Faults and problems noted in the written report are resolved Follow-up Moderator ensures that every issue raised has been resolved |
| Involved in inspection | An inspection team has four members Moderator (manager and leader of inspection team) A member of the team performing the current workflow A member of the team performing the next workflow A member of the SQA group |
| Special roles inspection | Special roles are played by the Moderator Both manager and leader Reader Leads team through Recorder Responsible for producing a written report of detected faults |
| FFP Metric. | For cost estimation of medium-scale data processing products |
| Three FFP Metric elements | Files Collection of logically or physically related records permanently resident in the product; transaction and temporary are excluded Flows A data interface between the product and the environment, e.g. a screen or a report |
| Three FFP Metric elements | Processes Functionally defined logical or arithmetic manipulation of data, e.g. sorting, validating or updating |
| FFP | S= fi+fl+pr C= d* S |
| COCOMO | Step 1. Estimate the length of the product in KDSI Step 2. Estimate the product development mode Organic: Small and straightforward Semidetached: Medium sized Embedded: Complex Step 3. Compute the nominal effort |
| Three types of classes | Entity classes – models information that is long lived Boundary classes- models interaction between the software product and its actors (input/output) Control classes – models complex computations and algorithms |
| Methods of entity class extraction (1) | Noun extraction A two-stage process: Stage 1. Concise problem definition: Describe the software product in single paragraph Stage 2. Identify the nouns: Identify the nouns in the informal strategy |
| Methods of entity class extraction (2) | CRC Cards For each class, fill in a card showing: Name of Class Functionality (Responsibility) List of classes it invokes (Collaboration) Post-It notes can be used CRC cards can be automated (CASE tool component) |
| CRC strength & weakness | Strength CRC cards are a powerful tool for highlighting missing or incorrect items Relationships between classes can be clarified Weakness If CRC cards are used to identify entity classes, domain expertise is needed |
| Chief programmer team approach | Chief Programmer: Successful manager and highly skilled programmer Back-up programmer: The back-up programmer must be in every way as competent as the chief programmer Programming secretary: Responsible for maintaining the program production library |
Created by:
Zeni
Popular Computers sets