In: Mechanical Engineering
Apply the principles of System Engineering to a real-world situation. Select an engineering opportunity. Frame the engineering opportunity in a system-engineering context. Define the system engineering process. Define the system engineering methodology. Use the following elements below:
Systems engineering is a methodical, disciplined approach for the design, realization, technical management, operations, and retirement of a system. A “system” is a construct or collection of different elements that together produce results not obtainable by the elements alone. The elements, or parts, can include people, hardware, software, facilities, policies, and documents; that is, all things required to produce system-level results. The results include system-level qualities, properties, characteristics, functions, behavior, and performance. The value added by the system as a whole, beyond that contributed independently by the parts, is primarily created by the relationship among the parts; that is, how they are interconnected. It is a way of looking at the “big picture” when making technical decisions. It is a way of achieving stakeholder functional, physical, and operational performance requirements in the intended use environment over the planned life of the systems. In other words, systems engineering is a logical way of thinking.
System Engineering of Automated Teller Machine
An Automated Teller Machine System is a safety-critical and real-time system that is highly complicated in design and implementation. It is a computerized telecommunications device that provides the clients of a financial institution with access to financial transactions in a public space without the need for a cashier, human clerk or bank teller. On most modern ATMs, the customer is identified by inserting a plastic ATM card with a magnetic stripe or a plastic smart card with a chip that contains a unique card number and some security information such as an expiration date or CVVC (CVV). Authentication is provided by the customer entering a personal identification number (PIN). This project is designed in such a way that the user has to enter pin number. Once verified, he/she is provided a menu and he/she has to enter the option provided in the menu. For example, when the user wants to withdraw cash, he/she has to enter the option for withdraw and from which account he/she wants to withdraw. After the option is entered along with the respective argument, if the transaction is possible the amount will be deducted from account and a message will be displayed on the screen. If the transaction is not possible an error message will be displayed on the screen.
PROJECT MANAGEMENT
In project management following
things must be done.
a. Project Planning and Scheduling
b. Risk Management
c. Estimation
In Project planning and scheduling, Planning of the project is done. In scheduling different task are schedule according to the deadline of the project.
A. Project Planning and
Scheduling
Project planning must deals with the following things.
a) Project Complexity: - Project complexity has a strong effect but
is heavily influenced by past practitioner experience.
b) Project Size: - As size increases the interdependency of
elements also grow.
c) The Degree of Structural Uncertainty: - the degree to which
requirements are solidified and the ease of functional
decomposition. The purpose of project planning is to ensure that
the end result is completed on time, within budget, and exhibits
quality.
B.Project Development Approach
Figure 1: Spiral model of software development
The Spiral model is an evolutionary
software process model that couples the iterative nature of
prototyping with the controlled and systematic aspects of the
linear sequential model. It provides the potential for rapid
development of incremental versions of the software. Using the
spiral model, software is developed in series of incremental
release. A spiral model is divided into a number of framework
activities, also called task regions. There are between three and
six task regions. Figure1 depicts a spiral model that contains six
task regions:
a) Customer communication – tasks required to establish effective
communication between developer and customer.
b) Planning – tasks required to define resources, timelines, and
other project related information.
c) Risk analysis – tasks required to assess both technical and
management risks.
d) Engineering – tasks required to build one or more
representations of the application.
e) Construction and release – tasks required to construct, test,
install, and provide user support.
f) Customer evolution – tasks required to obtain customer feedback
based on evolution of the software representations created during
the engineering stage and implemented during the installation
stage.
Each of the regions is populated by a set of work tasks, called a
task set, that are adapted to the characteristics of the project to
be undertaken. For small projects, the number of work tasks and
their formality is low. For larger, more critical projects, each
task region contains more work tasks that are defined to achieve a
higher level of formality. In our case, we have to provide medium
level of formality for making a good project report. We will take
decision about cost, schedule and number of iterations required to
complete the software.incremental versions of the software. Using
the spiral model,software is developed in series of incremental
release.
Feasibility Study
a. Technical
b. Feasibility
c. Economical Feasibility
d. Operational Feasibility
A. Technical Feasibility:
In Technical Feasibility study, one has to test whether the
proposed system can be developed using existing technology or not.
It is planned to implement the proposed system using java
technology. It is evident that the necessary hardware and software
are available for development and implementation of the proposed
system. Hence, the solution is technically feasible.
B. Economic Feasibility:
As part of this, the costs and benefits associated with the
proposed system compared and the project is economically feasible
only if tangible or intangible benefits outweigh costs. The system
development costs will be significant. So the proposed system is
economically feasible.
C. Operational Feasibility:
It is a standard that ensures inter operability without stifling
competition and innovation among users, to the benefit of the
public both in terms of cost and service quality. The proposed
system is acceptable to users. So the proposed system is
operationally feasible.
Data Flow
Diagram
Data Flow Diagrams are the
central tool and the basis from which other components are
developed. The transformation of data from input to output,
processes, may be described logically and independently of the
physical components associated with the system. The DFD is also
known as a data flow graph or a bubble chart. A graphical tool used
to describe and analyze the moment of data through a system manual
or automated including the process, stores of data, and delays in
the system. Data Flow Diagrams are the central tool and the basis
from which other components are developed. The transformation of
data from input to output, through processes, may be described
logically and independently of the physical components associated
with the system. The DFD is also known as a data flow graph or a
bubble chart.
Figure 2 .
level 1 Data Flow Diagram
Level 1 diagram
The level 1 diagram is often called a ―context diagram”. It
contains a single process, but it plays a very important role in
studying the current system. The context diagram defines the system
that will be studied in the sense that it determines the
boundaries. Anything that is not inside the process identifies the
context diagram will not be part of the system study.
Figure 3 . Entity Relationship (E-R) Diagram
E-R Diagram
In this E-R diagram, Customer, Current Account and Saving Account
are entities. Customer entity has Customer number (primary key),
pin attributes. Account number (as primary), Customer number,
Account balances are attributes of Current Account, similarly
Saving Account also has attributes like Account number ( as primary
key), Customer number, Account balances. Customer and Saving
Account have two relations one to one withdraw and one to one
deposit relation. Customer and Current Account also have two
relations one to one withdraw and one to one deposit relation.
Structure
diagram
Structure diagrams emphasize the things that must be present in the
system being modeled. Since structure diagrams represent the
structure, they are used extensively in documenting the software
architecture of software systems.
Figure 4. Structure diagram
Interface Testing
Interface sting is integral part of integration. We examined the
code to be tested and explicitly list each call to an external
component. In the system standards tests for GUIs have been
performed, which are as follows: a. The position and related labels
for all controls were checked. b. Validations for all inputs were
done. c. Pull down controls was verified for proper functionality.
d. Whether the non-editable text controls disabling and it was also
verified that it doesn’t exceed the maximum allowed length.
Performance
Testing
Performance testing is designed to test the runtime performance of
the system within the context of the system. These tests were
performed as module level as well as system level. Individual
modules were tested for required performance.
Advantages of Proposed
System
a. Very fast and accurate.
b. No need of any extra manual effort.
c. No fever of data loss.
d. Just need a little knowledge to operate the system.
Future
Enhancement
a. We can implement ATM System as client/server system. So all the
data will be stored in the single machine, and for any purpose all
the data will be retrieved from this central database.
b. So there will be no human work require for the employee. There
will be only one person required who will maintain this central
database.
c. Pin change, cell phone recharge facilities will be added to the
system.