Documente Academic
Documente Profesional
Documente Cultură
MANAGEMENT
II
REQUIREMENTS
Requirements: Functional and
ANALYSIS
Non-Functional,
AND
SPECIFICATION
User requirements, System
Structured
system
Analysis,
Petri
Nets-
Data
Dictionary.
UNIT
III
SOFTWARE
DESIGN
Design process Design Concepts-Design Model Design Heuristic Architectural Design
Architectural styles, Architectural Design, Architectural Mapping using Data Flow- User
Interface Design: Interface analysis, Interface Design Component level Design: Designing Class
based components,
traditional
Components.
UNIT
IV
TESTING
AND
IMPLEMENTATION
Software testing fundamentals-Internal and external views of Testing-white box testing- basis
path testing-control structure testing-black box testing- Regression Testing Unit Testing
Integration Testing Validation Testing System Testing And Debugging Software
Implementation Techniques:
Coding
practices-Refactoring.
UNIT
V
PROJECT
MANAGEMENT
Estimation FP Based, LOC Based, Make/Buy Decision, COCOMO II - Planning Project
Plan, Planning Process, RFP Risk Management Identification, Projection, RMMM - Scheduling
and Tracking Relationship between people and effort, Task Set & Network, Scheduling, EVA Process and Project Metrics.
16 MARK QUESTIONS
Unit 1
1. Discuss the various life cycle models in software development. (APR/MAY 2011)
2. Discuss in detail about any two evolutionary process models (May/June 2014)
3. Explain the prototype paradigm in process models. (May/June 2014)
4. Compare and contrast the different life cycle models (Nov/Dec 2011)
5. Describe the steps involved in Risk management
Unit 2
4. Draw use case and data flow diagram for a restaurant system. The activities of
the restaurant system are listed below: (May/Jun 2015)
Receive the customer food orders, Produce the customer ordered foods,
serve the customer with their ordered foods, collect payment from
customers, store customer payment details, order raw materials for food
products, pay for raw materials and pay for labour
Unit 3
1.
Discuss the process of translating the analysis model into a software design. ( APR/MAY
2011)
2.
Discuss the design heuristics for effective modularity design. (May/June 2013)
3.
4.
5.
Explain clearly the concept of coupling and cohesion? For each type of coupling
give an example of two components coupled in that way? (Nov/Dec 2011)
6.
Explain various cohesion and coupling methods used in software design. (May/Jun
2015)
7.
For a case study of your choice show the architectural and component design.
(May/Jun 2015)
Unit 4
1.
Write a note on equivalence partitioning and boundary value analysis of black box
testing. (APR/MAY 2011)
2.
What is unit testing? Why is it important? Explain the unit test considerations and
test procedure. (APR/MAY 2011) (May/June 2013)
3.
4.
5.
Write elaborately on white box testing for a software. How do you develop
test suites? (Nov/Dec 2012)
6.
Describe the various black box and white box techniques. Use suitable
examples for your explanation. (May/Jun 2015)
7.
Unit - 5
1. Explain the use of COCOMO model. (May/June 2013)
2. Describe the steps involved in project scheduling process (May/June 2013)
3. What are the categories of software risk? Give an overview about risk
management. (May/June 2014)
4. Calculate the effort and duration using the above details for the basic
COCOMO model (Nov/Dec 2011)
Given,
Number of user inputs=15
Number of user outputs=3
Number of external interfaces=11
1
Project scheduling
(ii)