CUSTOMER_CODE
SMUDE
DIVISION_CODE
SMUDE
EVENT_CODE
OCTOBER15
ASSESSMENT_CODE BC0057_OCTOBER15
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
6065
QUESTION_TEXT
Explain the Unified Approach in detail.
SCHEME OF
EVALUATION
Explanation of the processes :
Introduction and Use-case driven development (2 marks)
Object-oriented analysis (2 marks)
Object (oriented design (2 marks)
Iterative development and prototyping (2 marks)
Continuous testing (2 marks)
The Unified Approach (UA) combines the best practices, processes,
methodologies, and guidelines along with UML notations and
diagrams for better understanding object-oriented concepts and
system development.
The unified approach to software development revolves around the
following processes and concepts. The processes are:
∙ Use-case driven development
∙ Object-oriented analysis
∙ Object-oriented design
∙ Iterative development and prototyping
∙ Continuous testing
The methods and technology employed include:
∙ Unified modeling language used for modeling. Layered approach
∙ Repository for object-oriented system development patterns and
frameworks
∙ Component-based development
Object-Oriented Analysis
Analysis is the process of extracting the needs of a system and what
the system must do to satisfy the users' requirements. The goal of
object- briented analysis is to first understand the domain of the
problem and the system's responsibilities by understanding how the
users use or will use the system. OOA process consists of the
following steps:
1. Identify the Actors
2. Develop a simple business process model using UML Activity
diagram
3. Develop the Use Case
4. Develop interaction diagrams
5. Identify classes
Object-Oriented Design
∙ OOD Process consists of:
∙ Designing classes, their attributes, methods, associations, structures
and protocols, apply design axioms
∙ Design the Access Layer
∙ Design and prototype User Interface
∙ User Satisfaction and Usability Test based on the Usage / Use Cases
∙ Iterate and refine the design
∙ Iterative Development and Continuous Testing
You must iterate and reiterate until, eventually, you are satisfied
with the system. During this iterative process, your prototype will be
incrementally transformed into the actual application. The UA
encourages the integration of testing plans from day one of the
project. Usage scenarios can become test scenarios; therefore, use
cases will drive the usability testing. Usability testing is the process
in which the functionality of software is measured.
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
6067
QUESTION_TEXT
Explain in detail about different UML views.
SCHEME OF
EVALUATION
Explanation of
Use case view (2 marks)
Design view (2 marks)
Implementation view (2 marks)
Process view (2 marks)
Deployment view (2 marks)
Use Case View: The use case view of a system encompasses the use
cases that describe the behavior of the system as seen by its end
users, analysts, and testers. This view doesn't really specify the
organization of a software system. Rather, it exists to specify the
forces that shape the system's architecture. With the UML, the static
aspects of this view are captured in use case diagrams; the dynamic
aspects of this view are captured in interaction diagrams, statechart
diagrams, and activity diagrams.
Design View: The design view of a system encompasses the classes,
interfaces, and collaborations that form the vocabulary of the
problem and its solution. This view primarily supports the
functional requirements of the system, meaning the services that the
system should provide to its end users. With the UML, the static
aspects of this view are captured in class diagrams and object
diagrams: the dynamic aspects of this view are captured in
interaction diagrams, state-chart diagrams, and activity diagrams.
Process View: The process view of a system encompasses the threads
and processes that form the system's concurrency and
synchronization mechanisms. This view primarily addresses the
performance, scalability, and throughput of the system. With the
UML, the static and dynamic aspects of this view are captured in the
same kinds of diagrams as for the design view, but with a focus on
the active classes that represent these threads and processes.
Implementation View: The implementation view of a system
encompasses the components and files that are used to assemble and
release the physical system. This view primarily addresses the
configuration management of the system's releases, made up of
somewhat independent components and files that can be assembled
in various ways to produce a running system. With the UML, the
static aspects of this view are captured in component diagrams: the
dynamic aspects of this view are captured in interaction diagrams,
statechart diagrams, and activity diagrams.
Deployment View: The deployment view of a system encompasses
the nodes that form the system's hardware topology on which the
system executes. This view primarily addresses the distribution,
delivery, and installation of the parts that make up the physical
system. With the UML, the static aspects of this view are captured in
deployment diagrams: the dynamic aspects of this view are captured
in interaction diagrams, statechart diagrams, and activity diagrams.
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
72505
QUESTION_TEXT
What are patterns? Explain different types of patterns.
SCHEME OF
EVALUATION
A pattern is [an] instructive information that captures the essential
structure and insight of a successful family of proven solutions to a
recurring problem that arises within a certain context and system of
forces.
(2 ½ marks)
Types of patterns:
● Generative and Non-generative Patterns
● Anti-patterns
● Capturing Patterns
(Each point carries 2 ½ marks)
QUESTION_TYPE DESCRIPTIVE_QUESTION
QUESTION_ID
QUESTION_TEXT
112450
Explain the steps involved in Macro development process.
The macro development process consists of the following steps:
SCHEME OF
EVALUATION
1. Conceptualization. During conceptualization, you establish the
core requirements of the system. You establish a set of goals and
develop a prototype to prove the concept.
2. Analysis and development of the model. In this step, you use
the class diagrams to describe the roles and responsibilities
objects are to carry out in performing the desired behavior of the
system. Then, you use the object diagram to describe the desired
behavior of the system in terms of scenarios or alternatively, use
the interaction diagram to describe behavior of the system in
terms of scenarios.
3. Design or create the system architecture. In the design phase,
you use the class diagram to decide what classes exist and how
they relate to each other. Next, you use the object diagram to
decide what mechanisms are used to regulate how objects
collaborate. Then, you use the module diagram to map out where
each class and object should be declared. Finally, you use the
process diagram to determine to which processor to allocate a
process. Also, determine the schedules for multiple processes on
each relevant processor.
4. Evolution or implementation. Successively refine the system
through much iteration. Produce a stream of software
implementations (or executable releases), each of which is a
refinement of the prior one.
5. Maintenance. Make localized changes to the system to add new
requirements and eliminate bugs.
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
112455
QUESTION_TEXT
What are the components that should be clearly recognized on reading
a pattern?
SCHEME OF
EVALUATION
a.
Name
b.
Problem
c.
context
d.
Forces
e.
Solution
f.
Examples
g.
Resulting context
h.
Rationale
i.
Related patterns
j.
Known uses
QUESTION_TYPE
DESCRIPTIVE_QUESTION
QUESTION_ID
112457
QUESTION_TEXT
Explain the object oriented systems development activities.

Object oriented analysis – Use case driven

Object oriented design
SCHEME OF EVALUATION 


Prototyping
Component based development
Incremental testing