Part - A

1. What are the phases in traditional information system life cycle?

 Project planning, feasibility study: Establishes a high-level view of the intended project and determines its goals.
 Systems analysis, requirements definition: Defines project goals into defined functions and operation of the intended
application. Analyzes end-user information needs.
 Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process
diagrams, pseudocode and other documentation.
 Implementation: The real code is written here.
 Integration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and
interoperability.
 Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and
runs actual business.
 Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different
computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.
 2. Describe the correspondence between the traditional and object oriented paradigm.

Traditional versus Object-Oriented Paradigm

z In the past, systems analysis was a creative skill
– Individuality was highly prized
z Around 1970, large computers became affordable
– Information systems began to be developed by teams
– A systematic approach was needed
z The traditional methodology or traditional
paradigm was developed
– Also known as the structured methodology or structured
paradigm4
7
Traditional v. Object-Oriented Paradigm (contd)
z Initially, the traditional paradigm was successful
– Any approach is better than no approach at all
z During the 1980s
– Larger computers became affordable
– Information systems grew in size
z But the larger the information system, the less
successful the traditional paradigm was
z What had gone wrong?
8
Traditional v. Object-Oriented Paradigm (contd)
z The traditional paradigm worked well with smallscale information systems
– About 5,000 lines of code
z But not with medium-scale information systems
– About 50,000 lines of code
z Or with large-scale information systems
– At least 500,000 lines of code
z Why? 5
9
Traditional v. Object-Oriented Paradigm (contd)
z Recall: The two basic building blocks of
information systems are
– Operations; and
– Data
z The traditional paradigm
– Concentrates on operations; and
– Largely ignores data
z The object-oriented paradigm gives equal weight
to operations and dat
3. List five core workflows of the Unified process.
There are five core workflows
– Requirements workflow
– Analysis workflow
– Design workflow
– Implementation workflow
– Test workflow

4. List out four phases of Unified process.

– Inception phase
– Elaboration phase
– Construction phase
– Transition phase

5. What is purpose of Inception phase?

The aim of the inception phase is to determine
whether the proposed information system is
economically viable
6. Define inheritance.
This concept indicates that one class (the superclass) provides some common or general behavior inherited by one or more
specific classes (the subclasses). The subclasses then provide more or different behavior beyond that defined in the
superclass
 7. Distinguish between packages and subsystems.
8. What are CRC cards?
Class Responsibility Collaboration (CRC) cards are a brainstorming tool used in the design of object-oriented software. They were
proposed by Ward Cunningham and Kent Beck. [1] They are typically used when first determining which classes are needed and how
they will interact.

CRC cards are usually created from index cards on which are written:

1. The class name

2. Its Super and Sub classes (if applicable)
3. The responsibilities of the class.
4. The names of other classes with which the class will collaborate to fulfill its responsibilities.
5. Author

9. What is business model?

10. What are the non functional requirements?
11. Draw UML notation for boundary class.
12. Define multiplicity.
13. Define Stereotypes.
14. Distinguish Verfication and validation.
15. What is testing?
16. What are the types of testing?
17. Define quality.
18. Define reuse.
19. What are the types of reuse?
20. What is the difference between accidental reuse and deliberate reuse?
21. Define Risk.

Part –B

1. List out differences between the traditional and object oriented paradigm.
2. Discuss about classes and objects.
3. Explain about object relationship in detail with example.
4. Explain about class diagram in detail with example
5. Discuss about use case diagram in detail with example.
6. Discuss about initial requirements in detail.
7. Apply requirements work flow to Osbert Oglesby case study.
8. Draw use case diagram, class diagram, state chart diagram, sequence diagram and collaboration diagram for Osbert
Oglesby.
9. Draw use case diagram, class diagram, state chart diagram, sequence diagram and collaboration diagram for MSG
Foundation class.
10. Explain about incremental class diagram.
11. Explain the methodology of extracting boundary classes.
12. Apply the process of extracting entity classes to MSG foundation case study.
13. Apply the process of extracting entity classes to Osbert Oglesby case study.
14. Discuss the process of allocation of operations to classes.
15. What are the phases in Unified process and explain each phase in detail.
16. Explain about CRC cards with example.
17. Explain about Non execution based and execution based testing.
18. Explain duration and cost estimation techniques in detail
19. Discus about Cost Benefit Analysis
20. Discus about Risk Analysis
21. Discuss about reuse.