-
Page 1 of 11
Contents K thi thng 06 nm 2008 .......................................................................................................... 2
K thi thng 12 nm 2008 .......................................................................................................... 2
K thi thng 06 nm 2009 .......................................................................................................... 2
K thi thng 06 nm 2010 .......................................................................................................... 3
K thi thng 12 nm 2010 .......................................................................................................... 3
K thi thng 06 nm 2011 .......................................................................................................... 4
K thi thng 12 nm 2011 .......................................................................................................... 4
K thi Thng 06 nm 2012 ......................................................................................................... 5
1/ Ni dung cn c trong cu tr li & thang im cho Rich Picture ........................................... 5
2/ Ni dung cn c trong cu tr li & thang im cho Use Case Diagram ................................ 6
3/ Ni dung cn c trong cu tr li & thang im cho Rich Picture v Use Case Diagram. ....... 6
1/ Tr li cho Rich Picture .......................................................................................................... 7
2/ Tr li cho Use Case Diagram ............................................................................................... 8
3/ Tr li cho Rich Picture & Use Case Diagram ........................................................................ 9
-
Page 2 of 11
Thng k nhng th loi c ''yu thch'' khi hi v Rich Picutre & Use Case
Diagram trong thi Examination Papers qua cc k thi ca cc nm nh sau:
im nm trong khong 15 - 40 im
u tin cho mt scenarios hoc mt dn xut, t s hi nhng cu sau:
( Chng ta ch yu focus vo cu hi tm p n chung nht, ngn nht cho cc loi cu
hi bn di; cn vic v th scenarios thay i nn ty tng loi scenarios m ta v cho ng.)
K thi thng 06 nm 2008
There are many tools available to the system developer to help understand system
requirements.
a) Describe the role of use case diagrams for determining information systems
requirements [10 marks]
b) Describe the role of rich pictures as a requirements gathering tool for the building
of information systems. [10 marks]
c) Discuss the importance of the requirements analysis stage for developing an
information system. In your answer examine why both use case modelling and
rich pictures can be important in determining system requirements. [20 marks]
K thi thng 12 nm 2008
a) Explain the role of rich pictures in understanding user requirements. [10 marks]
b) Explain the role of use case diagram scenarios in understanding system
requirements. [10 marks]
c) Discuss the relationship between use case diagrams and rich pictures to assist the
developer in carrying out effective requirements analysis. [20 marks]
K thi thng 06 nm 2009
Identify two modelling techniques with which you are familiar (e.g. Rich Pictures and
Use Case modelling) and for each one discuss how it supports the analyst in
understanding requirements at an early stage in the development process.
[15 marks]
-
Page 3 of 11
K thi thng 06 nm 2010
Rich Pictures and Use Cases are two modelling techniques that help the analyst
understand the requirements of a system.
(a) Using suitable examples from a case study known to you, describe how rich pictures
can be used to understand the environment and culture in which the system sits.
[10 marks]
(b) Discuss the relationship between Rich Pictures and Use Case modelling and how
each tool helps the analyst to carry out effective requirements analysis. In answering
this question, critically analyse the strengths and weaknesses of each tool.
[20 marks]
K thi thng 12 nm 2010
(a) Using suitable examples, describe the key elements the requirements analyst
should consider when drawing a Rich Picture. [10 marks]
(b) Explain why producing primary and secondary scenarios when using Use Case
modelling is essential to understanding the requirements of a system. [10 marks]
(c) Rich Pictures and Use Cases are different types of tools with different uses.
Examine these differences and discuss whether using different tools such as
Rich Pictures and Use Cases adds value to the overall requirements analysis
activity. [20 marks]
-
Page 4 of 11
K thi thng 06 nm 2011
a) Using the above case as an example, explain how use cases can help the
requirements analyst to understand the role actors play in using systems and how
alternative uses of systems can be recorded [10 marks]
b) The above scenario is just a small part of a wider social system. Making any
reasonable assumptions and using examples from the case, explain how a rich picture
can assist the analyst in understanding the environment in which this system sits.
[10 marks]
c) Discuss why it is important to use a range of tools to understand both the technical
and the social aspects of an information system [20 marks]
K thi thng 12 nm 2011
-
Page 5 of 11
K thi Thng 06 nm 2012
(a) Using examples from the case study, explain the purpose of scenarios in Use
Case modelling to understand system requirements. [10 marks]
(b) Again, using the case study outlined above, show how a rich picture can be
used to capture the environment in which the proposed system sits in terms of
actors, processes, structure, scrutiny and issues of conflict. [10 marks]
(c) Discuss why using Rich Pictures and Use Cases together adds greater value to the
carrying out requirements analysis. In your answer discuss weaknesses you have found
in using Use Case analysis and drawing Rich Pictures. [20 marks]
V y l nhng ni dung chng ta cn phi tr li trong cu tr li ca mnh nh
sau: (trch t solution examination December 2010 - dnh cho ging vin chm im)
1/ Ni dung cn c trong cu tr li & thang im cho Rich Picture
Fig 1
-
Page 6 of 11
2/ Ni dung cn c trong cu tr li & thang im cho Use Case Diagram
Fig 2
3/ Ni dung cn c trong cu tr li & thang im cho Rich Picture v Use
Case Diagram.
Fig 3
-
Page 7 of 11
Cn c vo 3 hnh trn, ti xut phn tr li i din nh sau:(tham kho t Internet, c th cha y nh p n mong mun.)
1/ Tr li cho Rich Picture
Rich picture is a technique that is used in human activity modelling. The main purposes
of rich picture are as follow
To describe organisation structures including goals and issues
To describe the process and activities of the organisation
To describe the activities and responsibilities of the people who are relating with
the organisation including staffs
To describe the organisation/actors purpose, desire, their worries and concerns
To describe the current situation including conflicts and problems conditions
Rich picture is a flexible technique and based on the people not methods. It has only a
few rules and very useful to learn the situation of existing business systems. People are
too much focus on the methodologies when they develop a system. They forget about
the most important things to consider. Without considering the people, both from user
side and developer side, the system cannot get achievement. Differ from the other
techniques like data flow diagram (DFD) and use case diagram; rich picture is designed
to show the interaction and relation of people involved in the system including their
wishes, purposes, fears and conflicts.
Requirements analysis play very important role in a project because projects can decide
success or failure by requirement analysis. Requirement analysis is one of the initial
states to develop a system. So if there is no good requirements analysis, the project
cannot get the achievement. Requirements analysis too much depends on the good
understanding of technical aspects and environment of the system. Nowadays, the
-
Page 8 of 11
analysts are using many tools and techniques to understand the technical and
environments of the system. Many tools and techniques are focused on the technical
aspects and there are few techniques to describe the people and environments, soft
things of systems. In my point of view, the requirement analysis needs to understand
both technical and environment of the systems. So analysts are using many techniques
to make requirements analysis of a system like DFD, ERD, ELH and many others
techniques.
In soft system methodology, rich picture is very useful to analysis the requirements of
the system. Rich picture can describe not only the technical aspects but also the
environment of the system clearly. Until I learn the rich picture and soft system
methodology, I need many diagrams/tools to make effective requirements analysis of
the system. However, after I learn rich picture and SSM, I knew rich picture is very
useful to analysis the requirements of the system. Rich picture is not a perfect technique
to make analysis. For example, rich picture cannot describe the time and sequence of
the system. Like the ways, I think there is no perfect technique which can make analysis
of the system perfectly. However, rich picture is very helpful to make the effective
requirements analysis my coursework.
2/ Tr li cho Use Case Diagram
Use case modelling is an important technique that is used in unified modelling language
(UML). The main purpose of the use case diagrams are as follows
To describe the actors who are related with the system or included in the system
To describe the relationship between the actors and the system
To describe the key activities, behaviour of the system
To describe the components of the system
To describe the objectives of the user
Use case is a hybrid technique between soft and hard techniques .Use cases are
concentrated on not only the system but also the actors. So both the developers and
users can see the system clearly. There are only two important things to create use
-
Page 9 of 11
case diagrams that are actors and use cases. Actors represent the people have relation
with the system and use cases represent the tasks or activities of the system. Most of
functional requirements can be described as use cases.Use case diagrams are very
popular in software industries and most of developers are familiar with the use case
diagrams. Use case diagrams are easy to describe the behaviour of the system and
users can also easy to understand.
Use case modelling is very important technique to make the requirements analysis of a
system. Use case diagrams are very useful to describe the functional requirements of
the system. Nowadays, most of software industries are using use case diagram to make
the requirements analysis of a system. This is an effective technique to show the
activities of the system. It can also use with not only with the traditional method but also
with the rapid development methods.
It is more focused on the technical aspects then environment of the system. But it
describes the actors who have the relationship with the system and their
responsibilities. Until I learn the use case diagrams, I used the data flow diagrams to
analyse the system. There are so many levels and too much documentation. However,
after I learnt the use case diagrams I knew that use case diagrams are clear and
concise to describe the system. Use case diagrams are very helpful to make the
requirements analysis my coursework.
3/ Tr li cho Rich Picture & Use Case Diagram
a. Similarities
Both the Use Case and the Rich Picture are modelling techniques used in the
requirement analysis phase when developing the system. They model and abstract the
system through analysing users views and opinions. We can see that gathering users
information about organization, work, and existing problems is basic step in creating a
use case or a rich picture. Their main purpose is to help the system developers
thoroughly understand users requirements.
-
Page 10 of 11
Use Cases and Rich Pictures can be used as tools for the system developers
communicate with the users because they are easy to understand. It can be clearly
seen that the Rich Picture uses normal drawing mechanism, which is very easy for
anyone to understand while the Use Case applies a very simple way to the describe
systems functions and the interaction between the user and the system.
Both Use Cases and Rich Pictures model the actors and the relationships between
actors and the system. However, there are some differences between the Rich Pictures
actors and Use Cases actors. The Rich Picture draws all actors involved in the system,
whereas the Use Case just draw actors who work directly with the system, exchange
data with the system, or use main functions of the system. Therefore, we did not bring
all the actors in the Rich Picture to the Use Case.
Both the Use Case and the Rich Picture define the boundary of the system. The Rich
Picture shows both the system and environment around the system, whereas, the Use
Case shows the system and its functions. In other words, the boundary of the system in
the Rich Picture is everything related to the system, but in the use case, it is the
systems functions. In the Rich Picture, the actors are a part of the system while in the
Use Case; the actors stand outside the system not in the boundary of the system -
and interact with the system.
b. Differences
The Rich Picture draws the current system, environment around the system, actors
concerns, and conflicts. From the Rich Picture, system developers study about the
current system, try to identify how the current system works, what people are concerned
about, who are important actors and what is the focus. In contrast, the Use Case is
used to present the future system and its functions. The system modelled in the Use
Case will be developed in the future as the improvement of the system modelled in the
Rich Picture.
The Rich Picture try shows the conflicts in the existing system but does not show a
solution for them, whereas, the Use Case do not show any conflicts in the system. The
main aim of the Use Case is define new systems functions which will solve the
-
Page 11 of 11
problems in the existing system. Considering the purpose of the Rich Picture and the
Use Case mentioned above, we could identify this difference more clearly.
The Rich Picture and the Use Case use different languages of description. The Rich
Picture follows no commonly syntax, usually consist of symbols, icons, or can contain
as much information as is considered important. In contrast, there are rules for drawing
and documenting the Use Case especially in the high level Use Case used in
Software Development. The reason is that the system modelled in the Rich Picture is a
human system with included many aspects, whereas, the Use Case models a non-
human system related to technical aspects.
The Rich Picture includes actors in the system, environment around the system and
focuses on analysis of human systems, whereas, the Use Case leaves the actors
outside and focus on how humans interact with a non-human system. In other words,
the Use Case models a technical system that serves the people working as modelled in
the Rich Picture.