Scribd
Upload
6 views

11 System Conception

The document discusses system conception and provides guidance on devising system concepts, elaborating concepts, and preparing problem statements. It includes an example case study of conceiving an Automated Teller Machine (ATM) system. Key aspects addressed in the problem statement for the ATM network include: designing software to support an automated banking network with both cashiers and ATMs shared between banks; ATMs will communicate with a central computer to clear transactions with banks; and the system must correctly handle concurrent account access while apportioning costs between banks.

Uploaded by

20cs068
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
6 views

11 System Conception

The document discusses system conception and provides guidance on devising system concepts, elaborating concepts, and preparing problem statements. It includes an example case study of conceiving an Automated Teller Machine (ATM) system. Key aspects addressed in the problem statement for the ATM network include: designing software to support an automated banking network with both cashiers and ATMs shared between banks; ATMs will communicate with a central computer to clear transactions with banks; and the system must correctly handle concurrent account access while apportioning costs between banks.

Uploaded by

20cs068
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Object Oriented Modeling and Design Chapter 11 : System Conception

11. System Conception


11.1 Devising a System Concept
Most ideas for new systems are extensions of existing ideas. Here are some ways to find new
concepts.

■ New functionality. Add functionality to an existing system.

■ Streamlining. Remove restrictions or generalize the way a system works.

■ Simplification. Let ordinary persons perform tasks previously assigned to specialists.

■ Automation. Automate manual processes.

■ Integration. Combine functionality from different systems.

■ Analogies. Look for analogies in other problem domains and see if they have useful ideas.

■ Globalization. Travel to other countries and observe their cultural and business practices.

11.2 Elaborating a Concept


Most systems start as vague ideas that need more substance. A good system concept must

answer the following questions.

■ Who is the application for?

You should clearly understand which persons and organizations are stakeholders of the new
system. Two of the most important kinds of stakeholders are the financial sponsors and the end
users.

■ What problems will it solve?

You should establish the scope of the application by determining which features will be in the new
system and which will not.

■ Where will it be used?

You should determine if the new system is mission-critical software for the organization,
experimental software, or a new capability that you can deploy without disrupting the workflow.
It is important to know if the software will be used locally or will be distributed via a network.

Compiled by Dr. Raviram V, Department of CSE, SSIT, Tumkur Page 1


Object Oriented Modeling and Design Chapter 11 : System Conception

■ When is it needed?

Two aspects of time are important. The first is the feasible time, the time in which the system can
be developed within the constraints of cost and available resources. The other is the required
time, when the system is needed to meet business goals.

■ Why is it needed?

You may need to prepare a business case containing the financial justification for the new system,
including the cost, tangible benefits, intangible benefits, risk, and alternatives. You must be sure
that you clearly understand the motivation for the new system.

■ How will it work?

You should brainstorm about the feasibility of the problem. You might need some prototyping and
experimentation.

11.2.1 The ATM Case Study


System concept for an Automated Teller Machine:

Develop software so that customers can access a bank’s computers and carry out their own

financial transactions without the mediation of a bank employee.

■ Who is the application for?

A software vendor develops the ATM application for financial institutions (Banks).

■ What problems will it solve?

The ATM software is intended to serve both the bank and the customer. For the bank, ATM
software increases automation and reduces manual handling of routine paperwork. For the
customer, the ATM is ubiquitous and always available, handling routine transactions whenever
and wherever the customer desires.

■ Where will it be used?

ATM machines are available at many stores, sporting events, and other locations throughout the
world.

■ When is it needed?

From an economic perspective, it is desirable to minimize the investment, maximize the revenue,
and realize revenue as soon as possible.

Compiled by Dr. Raviram V, Department of CSE, SSIT, Tumkur Page 2


Object Oriented Modeling and Design Chapter 11 : System Conception

■ Why is it needed?

A novel product could outflank competitors and lead to premium pricing.

■ How will it work?

We will adopt three-tier architecture to separate the user interface from programming logic, and
programming logic from the database. In reality, the architecture is n-tier.

11.3 Preparing a Problem Statement


A problem statement should state what is to be done and not how it is to be implemented. It
should be a statement of needs, not a proposal for system architecture. The requestor should
avoid describing system internals, as this restricts development flexibility. Performance
specifications and protocols for interaction with external systems are legitimate requirements.
Software engineering standards, such as modular construction, design for testability, and
provision for future extensions, are also proper.

Kinds of requirements.

11.3.1 The ATM Case Study


The following figure shows a problem statement for an automated teller machine (ATM) network.

Compiled by Dr. Raviram V, Department of CSE, SSIT, Tumkur Page 3


Object Oriented Modeling and Design Chapter 11 : System Conception

Design the software to support a computerized banking network including both human cashiers
and automatic teller machines (ATMs) to be shared by a consortium of banks. Each bank provides
its own computer to maintain its own accounts and process transactions against them. Cashier
stations are owned by individual banks and communicate directly with their own bank’s
computers. Human cashiers enter account and transaction data.

Automatic teller machines communicate with a central computer that clears transactions with the
appropriate banks. An automatic teller machine accepts a cash card, interacts with the user,
communicates with the central system to carry out the transaction, dispenses cash, and prints
receipts. The system requires appropriate recordkeeping and security provisions.

The system must handle concurrent accesses to the same account correctly. The banks will
provide their own software for their own computers; you are to design the software for the ATMs
and the network. The cost of the shared system will be apportioned to the banks according to the
number of customers with cash cards.

Compiled by Dr. Raviram V, Department of CSE, SSIT, Tumkur Page 4

You might also like