What are the two general characteristics of a design that naturally carry over from requirements?
Answer: The design is an evolution from requirements.
So the two general characteristics of
a) consistency and
b) completeness of requirements usually carry over to the design.
Software Engineering
- Consider the situation where you have the following 4 requirements for an employee information system: - response time for short queries must be less then 1 sec. - in defining employee record, user must be able to enter employee name and be prompted for all the remaining employee attributes that are needed for the employee record - employee information may be searched using either the employee number or employee’s last name. - only authorized (employee himself, managers in his/her chain of command, personnel) search will show employee salary, benefits, and family information.
- What is BDD?
- Give an example of software security problem related to software defect.
- What is software obfuscation?
- What are the three key project status indicators, EV, SV, and CV in earned value project status tracking methodology?
- List and discuss the elements of a project plan.
- Assume that the total complexity factor (TCF) for the software project is 1.1, the Unadjusted Function Point (UFP) for the project is 153 and the productivity figure is 20 function points per person-month. What is the function point (FP) for the project, and what is the estimated effort in person-months for this project?
- Consider the COCOMO project effort estimation methodology. What are the 8 project characteristics that you need to consider in order to decide the project mode?
- What are the three components of risk management?
- Using the Function Point methodology, compute the Unadjusted Function Point for an average project that has 10 external inputs, 7 external outputs, 5 external inquiries, 3 internal logical files, and 4 external interface files.
- What are the fours phases of project management?
- What is WBS, and what is it used for?
- What are the three attributes of a software project that are most often considered for trade-off decisions for project adjustment?
- What is a Kiviat chart, and when would you use it?
- Consider the COCOMO project effort estimation methodology. What are the three project modes?
- Consider the COCOMO project effort estimation methodology. Consider a software project that you estimated at 2 KLOC in size, believe that it should be Organic mode, and the arithmetic product of the 15 cost-drivers or PROD(f’s) is 1.2. What is the estimated effort in person months?
- Consider the COCOMO project effort estimation methodology. How do the 15 cost-drivers influence the initial effort estimate?
- What is usage-month?
- Give an example of a problem that may occur if a customer stays on a particular release, skips several maintenance fix releases, and then applies a fix release.
- What is a product sunset, and what is involved?
- What is a pre-requisite/co-requisite relationship of product maintenance and fix releases?
- What is a problem priority level and what is it used for?
- Explain the customer problem arrival curve in terms of customer usage of the product and fixes.
- What is the estimated effort field on the change request form used for?
- Who is responsible for the Support FAQ database?