v5i32 - International Journal of Computer Science and...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
International Journal of Computer Science and Applications, © Technomathematics Research Foundation Vol. 5, No. 3, pp 9 - 22 9 EXPLAINING OBJECT ORIENTED ANALYSIS (OOA) CONCEPTS TO MANAGERS OF AN ORGANIZATION K. V. DINESHA, P. G. B HAT Indian Institute of Information Technology, Bangalore, India dinesha@iiitb.ac.in, bhat.pg@gmail.com It is said that objects occur naturally, meaning that good Object Oriented (OO) model reflects reality. The person who best understands reality is the domain manager; unfortunately he is not computer savvy. This paper attempts to make the manager aware of fundamentals of OO thinking so that he/she feels confident of attempting a first cut OO model of the intended application. Every manager worries about what the proposed software should do for each of the stakeholders for whom the software is being developed. Experiments in industry have brought out that teaching domain specialists about use cases and object concepts make them enthusiastic about participating in the OO modeling of the application. All that is necessary is to expose OO thinking in a way that it reinforces their approach to handling complex situations in practice. This paper is an evangelistic attempt to make managers adapt to OO thinking while conceiving new applications, through easy to understand approach to concepts such as Objects and Use Cases. Keywords : Object Oriented Analysis, managers of end user departments, Objects, Use cases, Scenarios, Flow of Events, Boundary, Control and Entity objects, Objects interacting with each other, association, aggregation, composition, and inheritance. 1. INTRODUCTION Several OOA concepts are already used by the customers while analyzing, designing, and implementing the ‘non-software version’ or ‘manual version’ of their systems. The OO way of analyzing and designing a system emanates from designs and procedures to build large systems. Hence the Object Oriented thinking starts from the requirement phase. The OO concepts help us to think and communicate with the customers and end users. A high level model for the people involved in software development process is represented in fig.1 below.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Dinesha and Bhat 10 Fig. 1 Usually the managers from the end user departments constitute the domain representatives and software analysts constitute the software company representatives. The domain representatives should be able to communicate with the software analysts regarding their requirements with the confidence that a software system can be built as per their needs. The understanding that the concepts used by them in building, managing and maintaining manual syst ems also form the basis for building software system will hopefully give the required confidence and comfort level for the domain people while participating in gathering requirements along with software professional. In this article we attempt to give such an explanation. We explain the following concepts:
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 14

v5i32 - International Journal of Computer Science and...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online