A state transition diagram shows the states of a system and how it reacts to events.
2.
★ Midterm Spring 2010Lecture 10
A poorly designed interface can cause a user to make catastrophic errors is one of the motivations for GUI.
ATrue
BFalse
The handout lists catastrophic user errors from poor interfaces as a motivation for good GUI design.
3.
★ Midterm 2006Lecture 10
The prototyping model of software development is
AA reasonable approach when requirements are well defined.
BA useful approach when a customer cannot define requirements clearly
CThe best approach to use for projects with large development teams
DA risky model that rarely produces a meaningful product
Prototyping helps when the customer cannot state requirements clearly.
4.
★ Midterm past paperLecture 10
A poorly designed interface can cause a user to make catastrophic errors is one of the motivations for GUI.
ATrue
BFalse
CSometimes
DNone of the above
Avoiding user errors caused by poor interfaces is a key reason for good GUI design.
5.
★ Midterm Spring 2010Lecture 20
Interaction Diagrams depict the ------------- Behavior of the system
AStatic
BDynamic
CActive
DNon of the above
Interaction diagrams show how objects interact over time, i.e. dynamic behaviour.
6.
★ Midterm Spring 2010Lecture 21
Asynchronous massages are denoted
AHalf Arrow
BSimple Line
CFull Arrow
DNon of above
Asynchronous messages (signals) are drawn with a half arrow.
7.
★ Midterm Spring 2010Lecture 21
which one is not the type of massage which sequence diagram depict
ASynchronous
Basynchronous
CCreate
DUpdate
Sequence diagrams show synchronous, asynchronous, create and destroy messages, not 'update'.
8.
★ Midterm 2011Lecture 24
What would be the most suitable architecture to develop a commercial web page to do business transactions over the internet ?
AClient server model
BIsland model
CRAD model
DRepository model
Web transactions follow the client-server model with browsers as clients and the web server as server.
9.
★ Midterm past paperLecture 24
Layered architecture consists of:
AOne single layer
BMultiple layers
COnly hardware layer
DOnly software layer
A layered architecture is organized as multiple layers.
10.
★ Midterm past paperLecture 24
In layered architecture, which layers are closer to machine hardware?
AOuter layers
BMiddle layers
CInner layers
DInterface layers
Inner layers are closest to the hardware.
11.
★ Midterm past paperLecture 24
In layered architecture, outer layers communicate with inner layers through:
ADirect memory
BInterfaces
CHardware ports
DDrivers
Each layer uses the services of the layer below through its interface.
12.
★ Midterm past paperLecture 38
Equivalence classes are used to:
AIncrease memory
BDivide problem domain into classes for testing
CDelete bugs
DWrite documentation
Equivalence partitioning divides the input domain into classes for testing.
13.
★ Midterm past paperLecture 39
What is an infeasible path in a program?
AA path executed frequently
BA path executed only once
CA path never executed for any input data
DA path executed during debugging
An infeasible path cannot be executed by any input.
14.
★ Midterm past paperLecture 39
Which testing technique includes coverage schemes?
ABlack box testing
BWhite box testing
CIntegration testing
DSystem testing
Statement, branch and path coverage are white box techniques.
15.
★ Midterm past paperLecture 42
Debugging is considered:
AOnly an art
BOnly a science
CBoth art and science
DNeither art nor science
Debugging needs both systematic method and intuition.
16.
★ Midterm past paperLecture 43
Which error occurs when a program repeatedly displays the same message or data?
ALogical error
BLoop error
CSyntax error
DPointer error
Repeated output of the same data is a symptom of a loop error.
17.
★ Midterm Spring 2010
By following modern system engineering practices simulation of reactive systems is no longer necessary
ATrue
BFalse
Simulation is still needed to check the behaviour of reactive systems before they are built.
18.
★ Midterm Spring 2010
Control flow diagrams are
Aneeded to model event driven systems.
Brequired for all systems
Cused in place of data flow diagrams
Duseful for modeling user interfaces
Control flow diagrams model the events and control that drive event-driven systems.
19.
★ Midterm Spring 2010
A change becomes ------------- because of close presence of data and functions
ALocalized
BPrivate
CGlobal
DAccessible
In OO design data and the functions using it sit together, so a change stays local.
20.
★ Midterm Spring 2010
A complex System evolves from a
Asmaller system
Bmedium sysetem
Cbigger system
Dnon of the given
A complex system that works has evolved from a simpler, smaller system that worked.
21.
★ Midterm Spring 2010
Coupling is a measure of ----------------of a module or component.
AIndependent
BDependent
CCloseness
DAll of the given
The handout defines coupling as a measure of the independence of a module or component.
22.
★ Midterm Spring 2010
Software Maintenance phase involves
ADebugging
BAdding new features
Cmaking changes
Dall of the given
Maintenance covers fixing bugs, adding features and making other changes.
23.
★ Midterm Spring 2010
The hardest single part of building a software system is deciding precisely ----------- to build.
Awhat
BHow
CWhen
DWhy
Deciding exactly what to build (the requirements) is the hardest part.
24.
★ Midterm Spring 2010
In Sequence Diagrams the time required by the receiver object to process the message is denoted by an---------------
AActivation Box
BSimple Box
CArrow
DNon of the above
The activation box on a lifeline shows the time the receiver spends processing a message.
25.
★ Midterm Spring 2010
Identifying System Features include ------
Alog important information
Bconduct business
Canalyze business results
Dall of the above
System features cover logging information, conducting business, analysing results and interacting with other systems.
26.
★ Midterm Spring 2010
Which of the following is a fact finding method?
ASite visits
BPrototyping
CStudy of similar systems
DAll of given
Site visits, prototyping and studying similar systems are all fact-finding methods.
27.
★ Midterm Spring 2010
Windows mobile is a popular mobile operating system which seen commonly on PDAs. Which of the following category pair(s) best describe(s) it?
Aapplication software, embedded software
Bsystem software, web-based software
Capplication software, scientific software
Dsystem software, embedded software
An operating system is system software, and on PDAs it runs embedded in the device.
28.
★ Midterm Spring 2010
The Object Oriented approach
Aimproves the reusability of codes.
Bmakes objects less independent.
Cincreases testing time.
Dcomplicates mapping of a system model to an implementation model.
Encapsulated classes can be reused, so OO improves code reusability.
29.
★ Midterm 2011
Cohesion is about making sure each component does _____ thing and does it well .
Athree
Btwo
Cinfinite
Done
A cohesive component does one thing and does it well.
30.
★ Midterm 2011
Collaboration diagrams have basically two types of components: objects and ----------.
Amessages
Bmethods
Cclasses
Dnon of the above
A collaboration diagram consists of objects and the messages they exchange.
31.
★ Midterm 2011
Flow charts represent.
ASequence.
BRandom
CParallel
DNon of above
Flowcharts show a sequential flow of steps.
32.
★ Midterm 2011
what is the most important software quality of a web based transaction .
Aefficiency
BModularity
Cusability
DSecurity
Web-based transactions involve money and personal data, so security matters most.
33.
★ Midterm Spring 2010
The Data dictionary contain description of each software
AConfiguration item.
BData object
CDiagram
DNotation
A data dictionary describes each data object used in the analysis model.
34.
★ Midterm Spring 2010
a cohesion class is one which emphasize ------ unit of ------.
ASingle and multiple.
BMultiple and functionality
CFunctional and single
DSingle and functional
A cohesive class focuses on a single unit of functionality.
35.
★ Midterm Spring 2010
In sequence Diagram events are organized in a ------ time line
Avertical
Bhorizontal
CVertical and Horizontal
DNon of above
In a sequence diagram time runs down the page along vertical lifelines.
36.
★ Midterm Spring 2010
Software crisis came in 1960 what is the main reason to for the crisis
ASoftware development technique
BHardware
CSoftware
DNon of above
The crisis came from the lack of proper techniques for developing large software.
37.
★ Midterm Spring 2010
central role of the software requirement Document in entire development process is related to
AProject planning
BProject tracing
CChange control
DAll of above
The SRS is the basis for planning, tracking and controlling changes in a project.
38.
★ Midterm Spring 2010
The scope description establishes the ---------- between the system we are developing and everything else in the universe.
ABoundary
BSystem
Climitation
DNone of above
A scope description sets the boundary between the system and its environment.
39.
★ Midterm Fall 2006
Both the software engineer and customer take an active role in software requirements engineering-a set of activities that is often referred to as Requirement_______________
AManaging
BRecognition
CAnalysis
DModeling
Pressman calls these joint requirements engineering activities analysis.
40.
★ Midterm Fall 2006
_________ is a measure of independence of a module or component.
ACohesion
BCoupling
CLoop coupling
DLoop cohesion
The handout defines coupling as a measure of the independence of a module or component.
41.
★ Midterm Fall 2006
In the Functional design, the structure of the system revolves around __________
AFunctions
BSequences
CModels
DFlows
Functional (action-oriented) design decomposes the system around functions.
42.
★ Midterm Fall 2006
Use case is the part of designing phase of software engineering
ATrue
BFalse
Use cases capture requirements in the definition (analysis) phase, not design.
43.
★ Midterm Fall 2006
Three categories of risks are
Abusiness risks, personnel risks, budget risks
Bproject risks, technical risks, business risks
Cplanning risks, technical risks, personnel risks
Dmanagement risks, technical risks, design risks
Risks are grouped as project, technical and business risks.
44.
★ Midterm Fall 2007
Business model is the part of designing phase of software engineering development life cycle
ATrue
BFalse
The business (domain) model is built during analysis/definition, not design.
45.
★ Midterm Fall 2007
The best way to conduct a requirements validation review is to
AExamine the system
BHave the customer look over the requirements
CSend them to the design team
DUse checklist to examine the questions
A checklist of questions applied to each requirement gives a systematic validation review.
46.
★ Midterm Fall 2007
The system specification describes the
AFunction, performance and constraints of a computer-based system
Bimplementation of each allocated system
Ctime required for simulation
Delement software architecture
A system specification states the function, performance and constraints of a computer-based system.
47.
★ Midterm 2006
What makes requirements elicitation difficult?
Abounding scope
Bunderstanding user needs
Crequirements volatility
Dall of the above
Problems of scope, understanding and volatility all make elicitation difficult.
48.
★ Midterm 2006
Which of the items listed below is not one of the software engineering layers?
AProcess
BManufacturing
CMethods
DTools
The layers are quality focus, process, methods and tools; manufacturing is not one.
49.
★ Midterm 2006
What are the three generic phases of software engineering?
Adefinition, development, support
Bwhat, how, where
Cprogramming, debugging, maintenance
Danalysis, design, testing
The generic phases are definition (what), development (how) and support (change).
50.
★ Midterm 2006
Which of these items should be used to select a software process framework?
APeople
BProduct
CProject
DAll of the above
The choice of process depends on the people, the product and the project together.
51.
★ Midterm Spring 2006
In DFD we show the flow of data in a system.
ATrue
BFalse
A data flow diagram shows how data flows through a system.
52.
★ Midterm Spring 2006
Which of the followings is not part of software Engineering phases?
AVision
BDefinition
CDevelopment
DProcess
The phases are vision, definition, development and maintenance; process is not a phase.
53.
★ Midterm Spring 2006
Activity Diagram give a pictorial description of
AUse case
BObjects
CState of system
DAll of these.
Activity diagrams give a pictorial description of the flow of a use case.
54.
★ Midterm Spring 2006
Use Cases are the part of designing phase of software engineering
ATrue
BFalse
Use cases capture requirements in the definition (analysis) phase, not design.
55.
★ Midterm Spring 2006
In data flow diagram an external entity can store/update data in data store directly
ATrue
BFalse
In a DFD data can reach a data store only through a process, never directly from an external entity.
56.
★ Midterm Spring 2007
Software is a product and can be manufactured using the same technologies used for other engineering artifacts.
ATrue
BFalse
Software is developed or engineered, not manufactured like physical artifacts.
57.
★ Midterm Spring 2007
Ambiguity means _____________.
Aambiguity means that two different readers of the same document interpret the requirement differently
Bambiguity means that two different writers of the same document interpret the requirement differently
Cambiguity means that different readers of the different documents interpret the requirement differently
Dboth "b" and "c"
A requirement is ambiguous when different readers of the same document interpret it differently.
58.
★ Midterm Spring 2007
The current software crisis was caused by the Y2K problem whose seeds were first sown by careless programmers in the early 1970's.
ATrue
BFalse
The software crisis was recognised in the 1960s, long before Y2K, and has broader causes.
59.
★ Midterm past paper
By following modern system engineering practices simulation of reactive systems is no longer necessary.
ATrue
BFalse
CSometimes true
DNone of the above
Reactive systems still need simulation to check their behaviour.
60.
★ Midterm past paper
Windows Mobile is a popular mobile operating system commonly used on PDAs. Which category pair best describes it?
AApplication software, embedded software
BSystem software, web-based software
CApplication software, scientific software
DSystem software, embedded software
An operating system is system software, and on PDAs it is embedded.
61.
★ Midterm past paper
According to coding style guide, how should abbreviations and acronyms be written when used as names?
AAlways in uppercase
BAlways in lowercase
CShould not be uppercase
DWritten with numbers
Abbreviations in names should not be all uppercase, e.g. exportHtmlSource.
62.
★ Midterm past paper
Which of the following is the correct example of abbreviation usage in coding style?
AexportHTMLSource()
BxportHTMLSource()
CexportHtmlSource()
DEXPORTHTMLSOURCE()
Acronyms are written in mixed case, as in exportHtmlSource().
63.
★ Midterm past paper
What is system downtime?
ATime when system runs faster
BPeriod when system works normally
CPeriod when developers fix the system to make it running again
DTime when system is upgraded
Downtime is the period the system is out of service while being fixed.
64.
★ Midterm past paper
In object oriented naming conventions, names representing types should be:
AVerbs
BAdjectives
CNouns written in mixed case starting with uppercase
DNumbers
Type names are nouns in mixed case starting with uppercase, e.g. Account.
65.
★ Midterm past paper
Variable names should start with:
AUppercase letter
BLowercase letter
CNumber
DSymbol
Variable names are mixed case starting lowercase.
66.
★ Midterm past paper
How should constants be written according to naming conventions?
ALowercase letters
BMixed case
CUppercase with underscore
DNumbers only
Constants are all uppercase with underscores, e.g. MAX_SIZE.
67.
★ Midterm past paper
Method and function names should generally be:
ANouns
BVerbs
CAdjectives
DSymbols
Methods do something, so their names are verbs.
68.
★ Midterm past paper
Template types in C++ should be represented by:
ALowercase letters
BSingle uppercase letter
CNumbers
DMixed symbols
C++ template type names use a single uppercase letter, e.g. T.
69.
★ Midterm past paper
Private class variables should have which suffix?
A#
B@
C_
D$
Private class variables get an underscore suffix.
70.
★ Midterm past paper
According to naming conventions, all names in code should be written in:
AUrdu
BEnglish
CFrench
DAny language
All names should be in English.
71.
★ Midterm past paper
What is the main objective of software testing?
ATo prove software has no errors
BTo expose defects in software
CTo increase program size
DTo remove documentation
Testing aims to find defects, not prove their absence.
72.
★ Midterm past paper
A test is considered successful when:
AIt runs without errors
BIt discovers an error
CIt compiles successfully
DIt increases speed
A successful test is one that uncovers an error.
No MCQs match this filter.Is filter mein koi MCQ nahi.
1.
★ Midterm Spring 20102 marks
Define abstraction ?
Show answerJawab dekhein
Abstraction is a technique in which we build a model of an entity from its essential characteristics and ignore the inessential details. It helps manage complexity by letting us look at an entity's important external characteristics while hiding its internal details (hiding the internal details is called encapsulation).
2.
★ Midterm Spring 2010Lecture 222 marks
Is the design of software architecture a creative process?
Show answerJawab dekhein
Yes. Designing a software architecture is a creative and iterative process. The architect performs a number of activities (system structuring, control modelling, modular decomposition) that are not done in a fixed order or sequence, and chooses among many possible structures to satisfy the functional and non-functional requirements; there is no mechanical procedure that produces the design.
3.
★ Midterm Spring 20102 marks
Suppose you are working as a software engineer involved in the development of an e-commerce website. What are the 2 most important characteristics your software must have?
Show answerJawab dekhein
Security and reliability. An e-commerce site handles customer data and payments, so transactions and personal information must be protected from unauthorized access, and the site must work correctly and be available whenever customers want to use it. Usability is also important, but security is the most critical quality of web-based transactions.
4.
★ Midterm Spring 20103 marks
What is the purpose of collaboration diagrams?
Show answerJawab dekhein
Collaboration diagrams are interaction diagrams that depict the dynamic behaviour of a system. They show the objects that take part in a scenario, the links between them and the messages they exchange; messages are numbered (1, 2, 3, ...) to show their order and which operation calls which. They emphasise how objects are organised and interact with respect to organisational units or boundaries (for example the user interface or other systems), and they can show synchronous, asynchronous, create and destroy messages with the same notation as sequence diagrams.
5.
★ Midterm Spring 20103 marks
What is the difference between Aggregation and Association?
Show answerJawab dekhein
Association is a general relationship in which objects are linked and use each other but remain independent; each can exist without the other (for example a person uses a computer). Aggregation is a special whole-part ('has a' / 'part of') association that implies tighter coupling: one object is made up of the others (for example a car and its engine). If the two objects are tightly bound and one cannot meaningfully exist without the other, it is aggregation; if they are usually considered independent, it is association. In UML association is a plain line and aggregation has a diamond at the whole end.
6.
★ Midterm 2011
A student claims that his bag is the "container". Justify it with solid reason.
Show answerJawab dekhein
In Coad's method a container is an object that holds other objects (for example bin, box, folder, locker, shelf). A bag holds other objects such as books, pens and notebooks; these can be put in and taken out while the bag itself continues to exist, and the bag knows about its contents. So the bag is a container object, and its relationship with its contents is a whole-part (aggregation) relationship. It is a container but not a place, since not every container is a place.
7.
★ Midterm 2011
A company assemble fans. It takes wires, coils, magnets etc. and then assemble them. What technique should you use for this system. You can use any methodology.
Show answerJawab dekhein
Use object-oriented modelling with whole-part (aggregation) structures, for example Coad's methodology. The fan is the whole and the wires, coils, magnets and other components are its parts, so the Fan class aggregates Wire, Coil and Magnet objects with suitable multiplicities. The assembly itself can be modelled as a transaction that records which parts are assembled into which fan, and a generalization structure can be used if there are different kinds of fans or parts.
8.
★ Midterm 2011
A customer puts the items in cart, go to counter, pay cash to cashier and go out. In this case which is the "Participant"
Show answerJawab dekhein
The customer (and the cashier). In Coad's method an actor is a person or organisation, and a participant is the role an actor plays in the system. Here a person plays the role of customer, and the store employee plays the role of cashier, so both are participants; the purchase and the cash payment are transactions.
9.
★ Midterm Spring 20103 marks
How can we decrease coupling? Explain it.
Show answerJawab dekhein
Coupling is the degree of interdependence between modules, and it should be kept low. It can be decreased by: letting modules communicate only through small, well-defined interfaces and passing only the data they need as parameters; hiding each module's internal data and implementation (encapsulation / information hiding) instead of letting other modules access it directly; avoiding shared global data; and minimizing the number of messages in the protocol of a class, i.e. the number of other classes and operations it depends on. Keeping each module highly cohesive also helps reduce coupling.
10.
★ Midterm Spring 2010Lecture 203 marks
What is the purpose of interaction diagram?
Show answerJawab dekhein
Interaction diagrams model the dynamic behaviour of the system. They show how a group of objects collaborate to carry out a use case or scenario: which objects take part, the messages passed between them and the order of those messages. This helps to describe the message flow, to identify the operations (responsibilities) each class needs, and to validate the object model. UML has two kinds: sequence diagrams, which emphasise the time ordering of messages, and collaboration diagrams, which emphasise the structural organisation of the interacting objects.
11.
★ Midterm Spring 20102 marks
Define cohesion.
Show answerJawab dekhein
Cohesion is an internal property of a module: the degree to which the elements inside a module are related and work together to perform a single, well-defined task. A highly cohesive module does one thing and does it well. Cohesion describes intra-component linkages, whereas coupling describes inter-component linkages; a good design has high cohesion and low coupling.
12.
★ Midterm Spring 2010Lecture 182 marks
Keeping connie's case study in mind, as discussed in lecture, list down whole parts structures which were identified.
Show answerJawab dekhein
In the Connie's Convenience Store case study the whole-part structures identified were: a store as a whole is made up of cashiers, registers and items; a register contains a cash drawer; and a sale is made up of sale line items.
13.
★ Midterm Spring 2010
Define data flow diagram
Show answerJawab dekhein
A data flow diagram (DFD) is a graphical representation of how data flows through a system. It shows external entities (sources and sinks of data), processes that transform the data, data stores, and the data flows between them. It models what happens to the data, not control flow or timing, and a top-level DFD can be refined into more detailed levels.
14.
★ Midterm Spring 20102 marks
Adding user interface detail in the SRS is controversial a creative process i.e by adding GUI detail to the SRS document, focus shift from what to how (analysis design) do you agree
Show answerJawab dekhein
Partly. The SRS should describe what the system must do; detailed GUI design describes how, so adding it to the SRS shifts the focus from analysis to design and can fix design decisions too early, which is why it is controversial. On the other hand, customers understand and review requirements much better when they see screen layouts or prototypes. A balanced approach is to include only enough interface detail (or a prototype) to clarify the requirements and leave detailed GUI design to the design phase.
15.
★ Midterm Spring 2010Lecture 223 marks
What is the architecture design process explain briefly.
Show answerJawab dekhein
The architectural design process has three main activities: (1) System structuring - the system is decomposed into several principal interacting sub-systems and the communication between them is identified. (2) Control modelling - a model of the control relationships between the different parts of the system is established. (3) Modular decomposition - each identified sub-system is decomposed into modules. These activities are not necessarily done in a fixed order.
16.
★ Midterm Spring 20103 marks
What is textual analysis?
Show answerJawab dekhein
Textual analysis is a technique for identifying objects and classes, developed by Abbott and extended by Graham and others. The parts of speech in the text of the requirement specification are identified and each is modelled by a corresponding model component: common nouns suggest classes, proper nouns suggest objects (instances), verbs suggest operations or associations, adjectives suggest attributes, and phrases such as 'is a' and 'has a' suggest inheritance and aggregation.
17.
★ Midterm 2011Lecture 213 marks
Define Asynchronous Messages and Synchronous Messages.
Show answerJawab dekhein
A synchronous message is a 'call event' shown with a full (filled) arrowhead. It represents nested flow of control, usually implemented as an operation call: the caller waits for the called routine to complete before moving on. An asynchronous message is a 'signal' shown with a half arrow. It does not block the caller, which continues immediately. Asynchronous messages typically create a new thread, create a new object, or communicate with a thread that is already running.
18.
★ Midterm 2011
HOW DO YOU DETERMINE THAT AN OBJECT BELONGS TO CERTAIN CLASS?
Show answerJawab dekhein
A class defines the common structure (attributes) and behaviour (operations) of a set of similar objects; it specifies their interface and implementation. An object belongs to a class when it has the attributes and exhibits the behaviour defined by that class, i.e. it is an instance created from the class. So we decide an object's class by examining its state (what it knows) and its behaviour (what it does) and grouping it with objects that share the same structure and behaviour.
19.
★ Midterm 2011
What is behavior driven perspective of an object?
Show answerJawab dekhein
In the behaviour-driven perspective an object is defined by how it acts and reacts, in terms of its state changes and message passing. Its behaviour is completely defined by its actions. A message is an action one object performs on another to get a reaction, and the operations that clients may perform on an object are its methods. Objects are identified by the responsibilities (services) they provide.
20.
★ Midterm 2011
What is Textual Analysis? Explain it
Show answerJawab dekhein
Textual analysis is a technique for identifying objects and classes, developed by Abbott and extended by Graham and others. The parts of speech in the text of the requirement specification are identified and each is modelled by a corresponding model component: common nouns suggest classes, proper nouns suggest objects (instances), verbs suggest operations or associations, adjectives suggest attributes, and phrases such as 'is a' and 'has a' suggest inheritance and aggregation.
21.
★ Midterm 2011Lecture 22
What is Software Architecture?
Show answerJawab dekhein
Software architecture is the organisational structure of a system. It can be recursively decomposed into parts that interact through interfaces, relationships that connect the parts, and constraints for assembling the parts. Parts that interact through interfaces include classes, components and sub-systems. It establishes the overall structure of the system.
22.
★ Midterm 2011
What is the Cardinality of Object?
Show answerJawab dekhein
Cardinality is the number of occurrences of one object that can be related to occurrences of another object in a given relationship. One-to-one (1:1): an occurrence of A relates to only one occurrence of B and vice versa. One-to-many (1:N): one occurrence of A can relate to many occurrences of B, but each B relates to only one A (a mother can have many children). Many-to-many (M:N): an occurrence of A can relate to many occurrences of B and each B to many A (an uncle can have many nephews and a nephew many uncles). In UML it is shown as multiplicity on the ends of an association.
23.
★ Midterm 20113 marks
Purpose of collaboration diagram?
Show answerJawab dekhein
Collaboration diagrams are interaction diagrams that depict the dynamic behaviour of a system. They show the objects that take part in a scenario, the links between them and the messages they exchange; messages are numbered (1, 2, 3, ...) to show their order and which operation calls which. They emphasise how objects are organised and interact with respect to organisational units or boundaries (for example the user interface or other systems), and they can show synchronous, asynchronous, create and destroy messages with the same notation as sequence diagrams.
24.
★ Midterm 20113 marks
It is fact that good design makes maintenance easier. Which design principle help this to be achieved?
Show answerJawab dekhein
Modularity, together with abstraction and separation of concerns (information hiding). These principles divide the system into understandable modules whose changes are local in effect, giving high cohesion and low coupling, so that a change in one part does not affect other parts and maintenance becomes easier.
25.
★ Midterm 2011
To manage the complexity of the system we need to apply the principle of abstraction. Discuss briefly?
Show answerJawab dekhein
Abstraction means modelling an entity by its essential characteristics and ignoring inessential details. It helps manage the inherent complexity of a system by letting us look at the important external characteristics of each part while hiding its internal complexity (encapsulation). We can then deal with the system at a higher level, one abstraction at a time, without having to think about all the details at once.
26.
★ Midterm 2011Lecture 222 marks
Differentiate between architectural design and system architecture in a single line?
Show answerJawab dekhein
System architecture defines the overall high-level structure of the system (its major sub-systems and how they interact), whereas architectural design is the process of producing that structure; detailed design then deals with the internals of individual components.
27.
★ Midterm 2011Lecture 223 marks
What are architectural designs Process, explain briefly?
Show answerJawab dekhein
The architectural design process has three main activities: (1) System structuring - the system is decomposed into several principal interacting sub-systems and the communication between them is identified. (2) Control modelling - a model of the control relationships between the different parts of the system is established. (3) Modular decomposition - each identified sub-system is decomposed into modules. These activities are not necessarily done in a fixed order.
28.
★ Midterm Spring 2010Lecture 102 marks
Define Motivation of GUI
Show answerJawab dekhein
Motivations for good GUI design: system users often judge a system by its interface rather than its functionality; a poorly designed interface can cause a user to make catastrophic errors; and poor user interface design is the reason why so many software systems are never used.
29.
★ Midterm Spring 2010Lecture 183 marks
Keeping in mind the Connie's case study, what rule of thumbs was identified, list them down.
Show answerJawab dekhein
The 'Who I know' rules of thumb identified in the Connie's case study were: an actor knows about its participants (a person knows about its cashier role); a transaction knows about its participants (a session knows about its register and cashier); a transaction contains its transaction line items (a sale contains its sale line items); a transaction knows its sub-transactions (a session knows about its sales; a sale knows about its payments); a place knows about its transactions (a store knows about its sessions); a place knows about its descriptive objects (a store knows about its tax categories); and a container knows about its contents (a store knows about its cashiers, items and registers).
30.
★ Midterm Spring 20102 marks
To manage the complexity of the system we need to apply the principles of separation of concern. Discuss briefly
Show answerJawab dekhein
Separation of concerns means dealing with different individual aspects of a problem by considering each aspect in isolation and independently of the others. A complex system is divided into smaller pieces of lesser complexity, called modules, each handling one concern, so that each can be understood, developed and changed separately.
31.
★ Midterm Spring 20102 marks
What is elaborated Use case? Explain it
Show answerJawab dekhein
After the use case model is derived, each use case is elaborated by adding the details of the interaction between the user and the system. An elaborated use case contains: use case name, actors, summary, pre-conditions, post-conditions, extends, uses (includes), normal course of events, alternative paths, exceptions and assumptions.
32.
★ Midterm Spring 20103 marks
It is a fact that a good design makes maintenance easier. List a design principle which helps this to be achieved.
Show answerJawab dekhein
Modularity, together with abstraction and separation of concerns (information hiding). These principles divide the system into understandable modules whose changes are local in effect, giving high cohesion and low coupling, so that a change in one part does not affect other parts and maintenance becomes easier.
33.
★ Midterm Spring 20062 marks
Determine which of the following relationships is inheritance, generalization, association or aggregation. Beware that there may be 3-way or N-way associations so do not assume that any N-way relationship is inheritance. Also draw the object model diagram in each case.
a. A wheel has a tyre.
b. A file is a document file or an executable file.
Show answerJawab dekhein
a. Aggregation (whole-part): Wheel is the whole and Tyre the part; a diamond at the Wheel end, one wheel has one tyre. b. Inheritance (generalization): File is the superclass and DocumentFile and ExecutableFile are subclasses, drawn with a triangle on the File end.
1.
★ Midterm Spring 20105 marks
what parameters are used to measure and analyze design quality?
Show answerJawab dekhein
A design can be looked at from different angles, and the parameters used to measure its quality are efficiency (good use of resources such as time and memory), compactness (small, simple code), reusability (parts can be reused) and maintainability (easy to understand and change, with changes local in effect). These can conflict: a design that gives efficient, compact code may not be easy to maintain. So whether a design is good must be judged against the project and application requirements; maintainability is usually assessed through high cohesion and low coupling.
2.
★ Midterm Spring 2010Lecture 165 marks
How the objects are identified in Peter codd's technique?
Show answerJawab dekhein
In Coad's technique, after identifying the system purpose and features, objects are identified by selecting: (1) Actors - people and organisations that take part in the system (person, company, agency). (2) Participants - the roles actors play (cashier, customer, clerk, applicant). (3) Places - where things come to rest or that contain other objects (store, bank, airport, warehouse). (4) Transactions - the events the system must record, coming from a GUI, a monitoring object or another system (sale, order, payment, deposit, agreement). (5) Container objects - objects that hold other objects (bin, box, shelf, cash drawer); every place is a container but not every container is a place. (6) Tangible things - the remaining nouns of the problem domain found by 'walking through' the system (item, book, account, product, schedule).
3.
★ Midterm 20115 marks
What should be the technique to assign attributes for objects.
Show answerJawab dekhein
Attributes are assigned while establishing each object's responsibilities, using the 'What I know' question: for each object, ask what it needs to know (its state) to fulfil the system's purpose and features. Candidate attributes come from the requirement text (adjectives and possessive phrases such as 'customer's name'). Each attribute is placed in the class it most naturally describes; an attribute that has attributes of its own or is shared by several objects is modelled as a separate object or a relationship instead; derived values that can be calculated are not stored. For example, in the Connie's case study an item knows its number, description and price, and a sale knows its date and time.
4.
★ Midterm Spring 20105 marks
What is meant by "system's static View"? Discuss briefly.
Show answerJawab dekhein
The static view of a system describes its structure, which does not change over time: the classes and objects of the system, their attributes and operations, and the relationships between them (association, aggregation/composition and generalization/specialization). It is shown with class and object diagrams (the object model). It is the counterpart of the dynamic view, which shows behaviour over time using interaction (sequence and collaboration) diagrams and state diagrams.
5.
★ Midterm Spring 2010Lecture 225 marks
comparison of software architecture and Building architecture
Show answerJawab dekhein
Software architecture is similar to building architecture. When a house is built, the architect, general contractor, electrician, plumber, interior designer and landscaper each have a different view of the structure; the views are drawn differently but are related, and together they describe the building's architecture. In the same way, software architecture establishes the overall structure of a software system and is described through several related views for different stakeholders (for example logical, process, development and physical views). In both cases the architecture is decided early, is expensive to change later, and must satisfy functional and non-functional needs. A difference is that software is intangible and easier to change, so its architecture can be refined iteratively.
6.
★ Midterm Spring 201010 marks
Code example of High Coupling
Show answerJawab dekhein
High (tight) coupling means one module depends on the internal details of another. Example in Java:
class Account {
public double balance;
}
class Bank {
void transfer(Account from, Account to, double amount) {
from.balance = from.balance - amount;
to.balance = to.balance + amount;
}
}
Bank reads and writes Account's internal field directly, so any change to how Account stores its balance (or any new rule, such as checking for sufficient funds) forces changes in Bank and in every other class that touches the field. The coupling is reduced by making balance private and giving Account its own operations:
class Account {
private double balance;
void withdraw(double amount) { balance = balance - amount; }
void deposit(double amount) { balance = balance + amount; }
}
Now Bank only calls from.withdraw(amount) and to.deposit(amount) and does not depend on Account's representation.
7.
★ Midterm Spring 20105 marks
What should be the consideration for the maintainable design?
Show answerJawab dekhein
To be maintainable a design must be understandable, and changes must be local in effect, so that a change in one part of the system does not affect other parts. This is achieved by applying the principles of modularity, abstraction and separation of concerns (with information hiding). Applied properly, they produce modules that are highly cohesive and loosely coupled, with simple structure and well-defined interfaces, which makes the design easy to maintain.
8.
★ Midterm Spring 20105 marks
Discuss the relation between sequence diagram & logical complexity.
Show answerJawab dekhein
Diagrams are meant to make interactions clear, so conditional logic in a sequence diagram needs special attention. If the logic is simple, it can be shown on the diagram (for example as guard conditions) without harm. If the logic is complex, putting it in the sequence diagram makes it cluttered and hard to understand; instead, draw separate sequence diagrams for the different scenarios, or show the complex logic with separate diagrams such as flowcharts or activity diagrams.
9.
★ Midterm 20115 marks
Law of balancing act in software
Show answerJawab dekhein
Software engineering is a balancing act. A software engineer has to balance many characteristics such as cost, efficiency, reliability and user-friendliness, which often conflict: making software more user-friendly may reduce its efficiency, and making it cheaper may reduce its reliability. Typical tensions are cost vs. efficiency, cost vs. reliability and efficiency vs. user interface. The engineer must analyse which qualities matter most for the particular software and its users and make trade-offs to strike the right balance among these conflicting requirements.
10.
★ Midterm 2011Lecture 205 marks
Discuss some of the purpose of interaction diagram?
Show answerJawab dekhein
Interaction diagrams model the dynamic behaviour of the system. They show how a group of objects collaborate to carry out a use case or scenario: which objects take part, the messages passed between them and the order of those messages. This helps to describe the message flow, to identify the operations (responsibilities) each class needs, and to validate the object model. UML has two kinds: sequence diagrams, which emphasise the time ordering of messages, and collaboration diagrams, which emphasise the structural organisation of the interacting objects.
11.
★ Midterm Spring 20105 marks
What is action-oriented approach for Software Design?
Show answerJawab dekhein
In the action-oriented (functional) approach, the problem is decomposed according to the functionality requirements, so the decomposition revolves around functions. It focuses only on the functionality of the system and typically ignores the data until it is needed, and the data is shared among functions, which gives a centralized control mechanism. In contrast, the object-oriented approach decomposes around data and considers functionality and data together, with decentralized control. Because data and functions are separated, a change in data can affect many functions, so the action-oriented approach handles essential complexity and change less well than the OO approach.
12.
★ Midterm Spring 20105 marks
Collaboration Diagrams depict Dynamic behavior of the system, explain it.
Show answerJawab dekhein
Collaboration diagrams are interaction diagrams, so they show the dynamic behaviour of the system: how objects interact at run time to carry out a scenario. Objects are shown connected by links, and the messages sent along these links are numbered (1, 2, 3, ...) to show their sequence and which operation calls which other operation. They show how objects interact with respect to organisational units or boundaries, such as the user interface or other systems, and can show synchronous, asynchronous, create and destroy messages like sequence diagrams.
13.
★ Midterm Spring 2010Lecture 225 marks
Narrate some of the architectural design guidelines that can help in addressing non-functional requirements challenges.
Show answerJawab dekhein
Software architecture must address non-functional as well as functional requirements. Guidelines: Performance - localise operations to minimise sub-system communication, i.e. use self-contained modules so inter-module communication is minimal. Security - use a layered architecture with critical assets in the inner layers. Safety - isolate safety-critical components (keep them in a small number of sub-systems). Availability - build in redundancy, with redundant components in the architecture. Maintainability - keep the architecture simple, using fine-grain, self-contained components.
14.
★ Midterm Spring 20105 marks
What is the importance of Classification in identifying Classes and objects?
Show answerJawab dekhein
Classification is grouping objects with common structure and behaviour into classes. It is the basis for identifying classes: by noticing what objects have in common we can define a class once and reuse it for all its instances, and organise classes into generalization-specialization hierarchies. Good classification reduces complexity, makes the model easier to understand and navigate, promotes reuse of common attributes and operations through inheritance, and helps find missing or redundant classes. It is iterative, because a first classification is usually refined as understanding grows.
15.
★ Midterm Spring 20105 marks
Discuss the relationship between Sequence diagrams and logical complexity
Show answerJawab dekhein
Diagrams are meant to make interactions clear, so conditional logic in a sequence diagram needs special attention. If the logic is simple, it can be shown on the diagram (for example as guard conditions) without harm. If the logic is complex, putting it in the sequence diagram makes it cluttered and hard to understand; instead, draw separate sequence diagrams for the different scenarios, or show the complex logic with separate diagrams such as flowcharts or activity diagrams.
16.
★ Midterm Spring 20105 marks
What is the difference between Association and composition?
Show answerJawab dekhein
In association the objects are linked and interact but have no intrinsic relationship; each is independent and can exist without the other, and it is the weakest link between objects (a person and a car he drives). In composition an object is made up of smaller part objects, giving a strong whole-part relationship: the parts belong to only one whole and their lifetime depends on the whole, so they are created and destroyed with it (a house and its rooms). In UML association is a plain line and composition a line with a filled diamond at the whole end.
17.
★ Midterm 200425 marks
A food processor has the following motor control. It has a switch that is either in the On position, or Off position. When the motor is stationary and the switch is turned on, then power is applied to a starting coil, and the motor starts. After the motor starts, the power is applied to the running coil, and the motor continues to run. The motor has a heat sensor. If the motor becomes too hot due to overload, then the power to the motor is cut off, and the motor stops. When the motor has cooled down, and it is stationary, power is again applied first to the starting coil, and then to the running coil, when it is in motion.
a. Draw a state transition diagram for the system (10 marks)
b. Draw the message sequence diagram for the above system (10 Marks)
c. Draw a use case block diagram, to illustrate the above-described sequence of events in detail (i.e. the motor was started, run, it overheated, stopped, cooled, and again started and run) (5 Marks)
Show answerJawab dekhein
(a) State transition diagram. States: Off (stationary), Starting, Running, Stopped-Overheated (cooling). Transitions: Off --switch turned on [motor stationary] / apply power to starting coil--> Starting; Starting --motor in motion / apply power to running coil--> Running; Running --heat sensor: too hot / cut off power--> Stopped-Overheated; Stopped-Overheated --motor cooled down and stationary [switch on] / apply power to starting coil--> Starting; Starting or Running --switch turned off / cut off power--> Off; Stopped-Overheated --switch turned off--> Off.
(b) Message sequence diagram. Participants: User, Switch, Motor controller, Starting coil, Running coil, Heat sensor, Motor. User -> Switch: turnOn; Switch -> Controller: switchOn; Controller -> Starting coil: applyPower; Motor -> Controller: inMotion; Controller -> Starting coil: removePower; Controller -> Running coil: applyPower; Heat sensor -> Controller: tooHot; Controller -> Running coil: cutPower (motor stops); Heat sensor -> Controller: cooledDown; Motor -> Controller: stationary; Controller -> Starting coil: applyPower; Motor -> Controller: inMotion; Controller -> Running coil: applyPower. Time runs down the page along each lifeline.
(c) Use case block diagram. Actors: User (operator) and Heat sensor. Use cases inside the system boundary: Switch On, Start Motor (power to starting coil), Run Motor (power to running coil), Detect Overheating / Cut Off Power, Cool Down, Restart Motor, Switch Off. The User is connected to Switch On and Switch Off; Switch On includes Start Motor, which is followed by Run Motor; the Heat sensor is connected to Detect Overheating, which stops the motor, and to Cool Down, which leads to Restart Motor (start then run again), showing the full sequence started - run - overheated - stopped - cooled - started - run.
18.
★ Midterm 200410 marks
Briefly describe "Software Engineering Framework". Do provide examples and diagrams where necessary.
Show answerJawab dekhein
Software engineering is a layered technology resting on an organisational commitment to quality. The framework has four layers, drawn as stacked layers from bottom to top: (1) Quality focus - the foundation; total quality management and continuous process improvement. (2) Process - the glue that holds the layers together; it defines a framework of activities (for example communication, planning, modelling, construction, deployment), milestones, work products and quality assurance points, so that projects can be managed and controlled. (3) Methods - the technical 'how to' for each task: requirements analysis, design, coding, testing and support (for example use case modelling, object-oriented design). (4) Tools - automated or semi-automated support for the process and methods (for example CASE tools, compilers, configuration-management and testing tools). Umbrella activities such as project tracking, risk management, quality assurance and configuration management apply across the whole process.
19.
★ Midterm 200425 marks
Determine which of the following relationships are inheritance, association or aggregation. Be aware that there may be 3-way or N-way associations so do not assume that any N-way relationship is inheritance. Also draw the object model in each case.
a. A country has a capital (5 marks)
b. A dining philosopher is using a fork (5 marks)
c. A file is an ordinary file or a directory (5 marks)
Show answerJawab dekhein
a. Association: Country --has capital-- City, one-to-one (each country has one capital city and a city is the capital of at most one country); the capital is not a component of the country, so it is drawn as a plain line labelled 'has capital' with multiplicity 1 and 0..1. b. Association: Philosopher --uses-- Fork; a philosopher uses forks (two at a time) and a fork is used by one philosopher at a time, so it is a plain association line with multiplicities such as 1 and 0..2. c. Inheritance (generalization): File is the superclass and OrdinaryFile and Directory are subclasses, drawn with a triangle on the File end.
20.
★ Midterm Fall 200425 marks
Determine which of the following relationships are inheritance, association or aggregation. Be aware that there may be 3-way or N-way associations so do not assume that any N-way relationship is inheritance. Also draw the object model in each case.
a. A person uses a computer language on a project (5 marks)
b. Modems and keyboards are input/output devices (5 marks)
c. Object classes may have several attributes (5 marks)
Show answerJawab dekhein
a. Ternary (3-way) association among Person, ComputerLanguage and Project: one association (drawn with a diamond joining the three classes) with many-to-many multiplicities on each end, because a person may use several languages on several projects. b. Inheritance (generalization): InputOutputDevice is the superclass and Modem and Keyboard are subclasses. c. Aggregation: an ObjectClass is made up of Attributes; a diamond at the ObjectClass end with multiplicity 1 and many (0..*) attributes.
21.
★ Midterm Fall 200410 marks
Briefly describe "Software Engineering Phases". Do provide examples and diagrams where necessary.
Show answerJawab dekhein
Software development is divided into four phases, each answering a question: (1) Vision - why the system is needed; the business objectives and scope. (2) Definition - what the system must do; requirements gathering, analysis and specification. (3) Development - how the system will be built; design, coding and testing. (4) Maintenance - handling change after delivery; correcting faults (corrective), adapting to a new environment (adaptive), adding enhancements (perfective) and preventing problems (preventive). Umbrella activities such as project management, quality assurance, configuration management and documentation span all phases. A diagram shows the phases in sequence (Vision -> Definition -> Development -> Maintenance) with the umbrella activities drawn across them; for example, for a library system the vision is to automate lending, definition lists features such as issuing and returning books, development builds and tests them, and maintenance adds changes after release.
22.
★ Midterm Fall 200425 marks
A food processor has the following motor control. It has a switch that is either in the On position, or Off position. When the motor is stationary and the switch is turned on, then power is applied to a starting coil, and the motor starts. After the motor starts, the power is applied to the running coil, and the motor continues to run. The motor has a heat sensor. If the motor becomes too hot due to overload, then the power to the motor is cut off, and the motor stops. When the motor has cooled down, and it is stationary, power is again applied first to the starting coil, and then to the running coil, when it is in motion.
a. Draw a use case block diagram, to illustrate the above-described sequence of events in detail (i.e. the motor was started, run, it overheated, stopped, cooled, and again started and run) (5 Marks)
b. Draw a state transition diagram for the system (10 marks)
c. Draw the message sequence diagram for the above system (10 Marks)
Show answerJawab dekhein
(b) State transition diagram. States: Off (stationary), Starting, Running, Stopped-Overheated (cooling). Transitions: Off --switch turned on [motor stationary] / apply power to starting coil--> Starting; Starting --motor in motion / apply power to running coil--> Running; Running --heat sensor: too hot / cut off power--> Stopped-Overheated; Stopped-Overheated --motor cooled down and stationary [switch on] / apply power to starting coil--> Starting; Starting or Running --switch turned off / cut off power--> Off; Stopped-Overheated --switch turned off--> Off.
(c) Message sequence diagram. Participants: User, Switch, Motor controller, Starting coil, Running coil, Heat sensor, Motor. User -> Switch: turnOn; Switch -> Controller: switchOn; Controller -> Starting coil: applyPower; Motor -> Controller: inMotion; Controller -> Starting coil: removePower; Controller -> Running coil: applyPower; Heat sensor -> Controller: tooHot; Controller -> Running coil: cutPower (motor stops); Heat sensor -> Controller: cooledDown; Motor -> Controller: stationary; Controller -> Starting coil: applyPower; Motor -> Controller: inMotion; Controller -> Running coil: applyPower. Time runs down the page along each lifeline.
(a) Use case block diagram. Actors: User (operator) and Heat sensor. Use cases inside the system boundary: Switch On, Start Motor (power to starting coil), Run Motor (power to running coil), Detect Overheating / Cut Off Power, Cool Down, Restart Motor, Switch Off. The User is connected to Switch On and Switch Off; Switch On includes Start Motor, which is followed by Run Motor; the Heat sensor is connected to Detect Overheating, which stops the motor, and to Cool Down, which leads to Restart Motor (start then run again), showing the full sequence started - run - overheated - stopped - cooled - started - run.
23.
★ Midterm Fall 200615 marks
Consider the following Scenario :
A juicer blender has the following motor control. It has a switch that is either in the On position, or Off position. When the motor is stationary and the switch is turned on, then power is applied to a starting coil, and the motor starts. After the motor starts, the power is applied to the running coil, and the motor continues to run. The motor has a heat sensor. If the motor becomes too hot due to overload, then the power to the motor is cut off, and the motor stops. When the motor has cooled down, and it is stationary, power is again applied first to the starting coil, and then to the running coil, when it is in motion.
a) Draw a state transition diagram for the system
b) Draw the message sequence diagram for the above system
c) Draw a use case block diagram, to illustrate the above-described sequence of events in detail (i.e. the motor was started, run, it overheated, stopped, cooled, and again started and run
Show answerJawab dekhein
(a) State transition diagram. States: Off (stationary), Starting, Running, Stopped-Overheated (cooling). Transitions: Off --switch turned on [motor stationary] / apply power to starting coil--> Starting; Starting --motor in motion / apply power to running coil--> Running; Running --heat sensor: too hot / cut off power--> Stopped-Overheated; Stopped-Overheated --motor cooled down and stationary [switch on] / apply power to starting coil--> Starting; Starting or Running --switch turned off / cut off power--> Off; Stopped-Overheated --switch turned off--> Off.
(b) Message sequence diagram. Participants: User, Switch, Motor controller, Starting coil, Running coil, Heat sensor, Motor. User -> Switch: turnOn; Switch -> Controller: switchOn; Controller -> Starting coil: applyPower; Motor -> Controller: inMotion; Controller -> Starting coil: removePower; Controller -> Running coil: applyPower; Heat sensor -> Controller: tooHot; Controller -> Running coil: cutPower (motor stops); Heat sensor -> Controller: cooledDown; Motor -> Controller: stationary; Controller -> Starting coil: applyPower; Motor -> Controller: inMotion; Controller -> Running coil: applyPower. Time runs down the page along each lifeline.
(c) Use case block diagram. Actors: User (operator) and Heat sensor. Use cases inside the system boundary: Switch On, Start Motor (power to starting coil), Run Motor (power to running coil), Detect Overheating / Cut Off Power, Cool Down, Restart Motor, Switch Off. The User is connected to Switch On and Switch Off; Switch On includes Start Motor, which is followed by Run Motor; the Heat sensor is connected to Detect Overheating, which stops the motor, and to Cool Down, which leads to Restart Motor (start then run again), showing the full sequence started - run - overheated - stopped - cooled - started - run.
24.
★ Midterm Fall 200610 marks
The Process of Software Development involves construction and Management. Discuss each category in detail and draw diagram to show their relationship.
Show answerJawab dekhein
Construction activities are those directly related to building the software: requirements gathering and analysis, design, coding and testing (and deployment). Management activities are those that support and control construction: project planning and estimation, scheduling, staffing and organising the team, monitoring and controlling progress, risk management, quality assurance, configuration management and documentation. Management activities are umbrella activities that span all construction activities. Diagram: the construction activities drawn as a chain (Requirements -> Design -> Coding -> Testing) inside a larger box or band labelled Management (planning, tracking, QA, configuration management), showing that management surrounds and controls every construction activity.
25.
★ Midterm Fall 20065 marks
Briefly explain the key points (including benefits/drawbacks) about the Water Fall life-cycle model.
Show answerJawab dekhein
The waterfall model is a linear, sequential life-cycle: requirements analysis, design, implementation (coding), testing and maintenance, each phase completed and documented before the next begins, with output of one phase as input to the next. Benefits: simple and easy to understand and manage; clear milestones and documentation at each stage; works well when requirements are well understood and stable. Drawbacks: requirements must be fixed at the start, which is rarely possible; it is inflexible and costly to go back to an earlier phase; a working product appears only late, so problems are found late and the customer gives feedback late; it is risky for large or changing projects.
26.
★ Midterm Fall 200712 marks
List three necessary and one desired property of requirements: [4 Marks]
For each of the following given Requirement indicate whether it is Functional (F) or Non-Functional (N) Requirement. [2 marks each]
1. The System should be designed so it can later be extended to a Blue Line reservation System.
2. The System will allow the user to view the layout of seats in Bus.
3. The System must be available at all times.
4. A given seat can be assigned to only one person.
Show answerJawab dekhein
Necessary properties (any three): correct, complete, consistent, unambiguous, verifiable (testable). Desired property: prioritized (ranked for importance and stability); traceability or modifiability are also desired properties.
1. N - extensibility/maintainability (a quality of the system). 2. F - a service the system provides. 3. N - availability. 4. F - a rule on the system's seat-assignment behaviour.
27.
★ Midterm Fall 200710 marks
Requirement engineering mainly deals with the definition phase of the system. Discuss the importance of Requirement Engineering.
Show answerJawab dekhein
Requirements engineering establishes what the system must do and the constraints it must meet. It is important because: the hardest part of building software is deciding precisely what to build, and no other part cripples the system as badly if done wrong; errors in requirements are the most expensive to fix later, since their cost grows sharply in design, coding, testing and maintenance; a large share of project failures come from incomplete, changing or misunderstood requirements; the agreed requirements (SRS) form the contract between customer and developer and the basis for project planning, estimation, tracking, design, testing (acceptance criteria) and change control; and good elicitation, analysis, specification and validation ensure the delivered system meets the users' real needs, saving time and cost.
28.
★ Midterm Fall 200710 marks
Identify appropriate classes and methods for the following requirements specification, and draw the resulting class diagram:
"Customers order a number of items from a shop. The purpose of this system is to produce a printed invoice for the customers' orders. Each invoice should contain a full list of items ordered together with their price. Customers might order more than one of a particular item so the invoice should show the number of each item ordered rather than list them multiple times. The invoice should display the cost of each item and the total amount payable. The invoice should also print the customer's name and address."
Show answerJawab dekhein
Classes: Customer (name, address; placeOrder()); Order (date; addItem(item, quantity), getTotal()); OrderLine (quantity; getCost() = quantity x item price); Item (description, price; getPrice()); Invoice (printInvoice(), calculateTotal()). Class diagram: Customer 1 --places-- 0..* Order; Order 1 <>-- 1..* OrderLine (aggregation: an order is made of order lines); OrderLine 0..* --refers to-- 1 Item; Order 1 -- 1 Invoice (the invoice is produced for an order). The invoice prints the customer's name and address, each order line with item, quantity and cost, and the total amount payable.
29.
★ Midterm 2006Lecture 22
Discuss briefly the architectural attributes of software?
Show answerJawab dekhein
Software architecture must address non-functional as well as functional requirements. Guidelines: Performance - localise operations to minimise sub-system communication, i.e. use self-contained modules so inter-module communication is minimal. Security - use a layered architecture with critical assets in the inner layers. Safety - isolate safety-critical components (keep them in a small number of sub-systems). Availability - build in redundancy, with redundant components in the architecture. Maintainability - keep the architecture simple, using fine-grain, self-contained components.
30.
★ Midterm Spring 200516 marks
Consider the following requirements specification for a computerized appointments system for a doctors' surgery.
"The system will be primarily operated by the doctors' receptionists. They will make appointments for patients who contact the surgery. To make an appointment the receptionist gets the patient's name, checks that the patient is registered and gets the next available appointment slot. Providing this slot is acceptable to the patient the appointment is confirmed and the diary updated. The system should enable receptionists to cancel appointments either in response to patients' or doctors' requests. If a patient cancels a confirmed appointment within 24 hours, he has to pay 50 Rs. cancellation charges; patients who fail to turn up for an appointment must pay 100 Rs. charges. The system must prepare invoices for customers who have to pay charges. As the system is only to be used by receptionists or doctors it should have user friendly interface and an appropriate login procedure that will only allow authorized users to enter the system."
a) Identify all non-functional requirements. [2 marks]
b) Identify all the actors and use cases and draw the corresponding use case diagram. [6 marks]
c) Elaborate Make Appointment use case. Clearly identify the pre-condition, post- condition, normal course and the alternative courses. [8 marks]
Show answerJawab dekhein
a) Non-functional requirements: the system should have a user-friendly interface (usability), and it should have a login procedure that allows only authorized users (receptionists and doctors) to enter (security).
b) Actors: Receptionist (primary) and Doctor; the Patient interacts only through the receptionist. Use cases: Login, Make Appointment, Cancel Appointment, Prepare Invoice (for cancellation and no-show charges), with Check Patient Registration and Update Diary included by Make Appointment. Receptionist is linked to Login, Make Appointment, Cancel Appointment and Prepare Invoice; Doctor is linked to Login and Cancel Appointment (doctor's request).
c) Make Appointment - Actor: Receptionist. Pre-condition: the receptionist is logged in. Post-condition: an appointment is confirmed for the patient and the diary is updated. Normal course: 1. Patient contacts the surgery. 2. Receptionist enters the patient's name. 3. System checks that the patient is registered. 4. System shows the next available appointment slot. 5. Patient accepts the slot. 6. System confirms the appointment and updates the diary. Alternative courses: patient not registered - the receptionist registers the patient (or the use case ends); slot not acceptable - the system offers the next available slot until one is accepted or the patient declines, in which case no appointment is made.
31.
★ Midterm Spring 200510 marks
The UML includes: use case diagrams, use case description, object model, sequence diagrams and collaboration diagrams. Explain briefly what these are, making clear the relationships between them. [10 marks]
Show answerJawab dekhein
Use case diagram: shows the actors and the use cases (services) they use, giving the functional scope of the system. Use case description: a textual elaboration of each use case - actors, pre- and post-conditions, normal course and alternative courses. Object model (class diagram): the static structure - classes, attributes, operations and relationships (association, aggregation, inheritance). Sequence diagram: shows, in time order, the messages exchanged by objects to carry out one use case scenario. Collaboration diagram: shows the same interaction organised around the objects and their links, with numbered messages. Relationships: the use case diagram identifies the use cases; each is detailed by a use case description; the nouns and responsibilities in these descriptions give the classes of the object model; each use case scenario is then realised by objects of the object model in a sequence or collaboration diagram (two equivalent views of the same interaction), and the messages in these diagrams become operations of the classes, refining the object model.
32.
★ Midterm Spring 20065 marks
Explain the purpose (using only two sentence in each case) of each of the following components of UML
- Use case diagram
- Use case description
- Class diagram
- Sequence diagram
- Business or Domain model
Show answerJawab dekhein
Use case diagram: shows the actors and the use cases they perform, defining the functional scope of the system. It gives a high-level view of who uses the system for what.
Use case description: describes one use case in text - actors, pre- and post-conditions, normal and alternative flows. It details the interaction between user and system.
Class diagram: shows the classes with their attributes, operations and relationships. It models the static structure of the system.
Sequence diagram: shows the messages objects exchange in time order for one scenario. It models dynamic behaviour and helps find class operations.
Business or domain model: shows the important concepts of the problem domain and their relationships. It helps understand the business before designing the software.
33.
★ Midterm Spring 20065 marks
Consider the following requirements specification for a computerized appointments system for a doctors' surgery.
"The system will be primarily operated by the doctors' receptionists. They will make appointments for patients who contact the surgery. To make an appointment the receptionist gets the patient's name, checks that the patient is registered and gets the next available appointment slot. Providing this slot is acceptable to the patient the appointment is confirmed and the diary updated. The system should enable receptionists to cancel appointments either in response to patients' or doctors' requests. If a patient cancels within 24 hours of a confirmed appointment they have to pay a Rs. 10 cancellation charge; patients who fail to turn up for an appointment must pay a Rs. 20 charge. The system must prepare invoices for customers who have to pay charges. As the system is only to be used by receptionists or doctors, there will need to be an appropriate login procedure that only allows authorized users to enter the system."
a) Draw a use case diagram for the above system (one of your use cases should be "Make Appointment"). (6 marks)
b) Provide a narrative description for the "Make Appointment" use case including pre, post conditions and the main alternatives. (12 marks)
c) Draw the sequence diagram for the "Make Appointment" use case (you can assume that there are classes corresponding to "GUI", "Diary" and "Appointment" as well as a database of "Patients"). (7 marks)
Show answerJawab dekhein
a) Actors: Receptionist and Doctor. Use cases: Login, Make Appointment, Cancel Appointment, Prepare Invoice; Make Appointment includes Check Patient Registration. Receptionist is linked to Login, Make Appointment, Cancel Appointment and Prepare Invoice; Doctor is linked to Login and Cancel Appointment.
b) Make Appointment - Actor: Receptionist. Pre-condition: receptionist is logged in and the patient has contacted the surgery. Post-condition: an appointment is confirmed and recorded in the diary. Main course: receptionist enters the patient's name; system checks that the patient is registered; system finds the next available slot; patient accepts it; system creates the appointment, confirms it and updates the diary. Alternatives: patient not registered - register the patient first or end the use case; slot not acceptable - offer the next available slot until one is accepted, or end with no appointment if the patient declines.
c) Sequence: Receptionist -> GUI: enterPatientName(name); GUI -> Patients: checkRegistered(name); Patients -> GUI: registered; GUI -> Diary: getNextAvailableSlot(); Diary -> GUI: slot; GUI -> Receptionist: showSlot(slot); Receptionist -> GUI: confirm(slot); GUI -> Appointment: create(patient, slot); GUI -> Diary: update(appointment); GUI -> Receptionist: confirmation. Lifelines run down the page in this order.
34.
★ Midterm Spring 20066 marks
What is meant by functional requirements? For each requirement given below indicate whether it is a functional requirement (F) or a non-functional requirement (N)
1. The system should be designed so it can be later extended to handle a frequent-flyer plan.
2. The system will allow the user to view the layout of seat in an aircraft.
3. The system must be available at all times. Only 2 minutes of downtime is to be permitted.
4. A given seat can be assigned to at most one person at any given time.
Show answerJawab dekhein
Functional requirements state the services the system must provide: what it should do, how it should react to particular inputs and behave in particular situations. 1. N (extensibility). 2. F. 3. N (availability). 4. F.
35.
★ Midterm Spring 2007
Object models (as described for example using class diagrams) often incorporate the following relations:
- generalisation-specialisation (inheritance)
- whole-part (aggregation)
- association
- object is instance of class
Using whichever of these relations you feel is the most appropriate, draw simple diagrams to model the ideas in each of the following sentences (you should use the appropriate UML notation and include labels and numbers where appropriate).
i. JBuilder is a Java program
ii. A polygon is built from a number of points.
iii. A football team consists of 11 players and 5 substitutes.
iv. Mouse and keyboard are different input devices.
v. A class can have multiple attributes.
Show answerJawab dekhein
i. Object is instance of class: JBuilder is an object (JBuilder : JavaProgram, name underlined) with a dashed instance-of arrow to the class JavaProgram. ii. Aggregation: Polygon (whole, diamond end, 1) made of Point with multiplicity 3..*. iii. Aggregation: FootballTeam (whole) with two whole-part links, to Player with multiplicity 11 (labelled players) and to Player with multiplicity 5 (labelled substitutes), or to a Substitute class with multiplicity 5. iv. Generalisation: InputDevice superclass with subclasses Mouse and Keyboard (triangle at InputDevice). v. Aggregation: Class (whole, 1) made of Attribute with multiplicity 0..* (or 1..*).
36.
★ Midterm Spring 2007
Determine which of the following relationships are inheritance, association or aggregation. Be aware that there may be 3-way or N-way associations so do not assume that any N-way relationship is inheritance. Also draw the object model in each case.
a. Car and engine
b. A polygon is composed of an ordered set of points
c. Computer and its accessories like keyboard, mouse and monitor
Show answerJawab dekhein
a. Aggregation (whole-part): Car (whole, diamond) has one Engine; 1 to 1. b. Aggregation: Polygon (whole, diamond) composed of Point, multiplicity 3..* with the constraint {ordered} on the Point end. c. Aggregation: Computer (whole, diamond) with parts Keyboard, Mouse and Monitor, each with its own whole-part link and multiplicity (for example 1).
37.
★ Midterm Spring 2007
Software engineering is often characterized as "programming-in-the-large". List ten reasons why large projects present such a different challenge to "programming-in-the-small".
(You should list the ten you feel are the most important - do not give more than ten as any additional ones will not be considered).
Show answerJawab dekhein
1. Large teams need communication and coordination, and communication overhead grows with team size. 2. Requirements are complex, unclear and change during the project. 3. The system is too big for one person to understand, so it must be decomposed into modules with well-defined interfaces. 4. Planning, estimation, scheduling and tracking of time and cost are required. 5. Multiple stakeholders with conflicting needs must be managed. 6. Integration of many separately developed parts is difficult. 7. Configuration and version management of many files, releases and changes is needed. 8. Systematic testing and quality assurance are needed because errors are more numerous and costly. 9. Long life means maintenance and evolution by people other than the original developers, so documentation is essential. 10. Non-functional requirements (performance, reliability, security) and risk management become critical, and the project must follow a defined process.