Scribd
Upload
17 views

Systems Architecture, Documentation and Testing

book for systems architeture

Uploaded by

addokenneth58
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
17 views

Systems Architecture, Documentation and Testing

book for systems architeture

Uploaded by

addokenneth58
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 24

SYSTEMS

ARCHITECTURE
What is Systems Architecture?
System architecture translates the logical design of an information
system into a physical structure that includes hardware, software,
network support, processing methods, and security. It is a graphical
representation that depicts the physical implementation of software
system components (Read the es in the vle)
Items considered by a systems analyst when
selecting an appropriate architecture
a. Enterprise resource planning (ERP)
b. Initial and total cost of ownership (TCO)
c. Scalability
d. Web integration
e. Legacy system interface requirements
f. Processing options
g. Security issues
Enterprise resource planning (ERP)

• ERP considerations help to establish a company-wide strategy for IT


resources use. ERP helps define a specific architecture, including
standards for data, processing, network, and user interface design. An
advantage of ERP is that it describes a specific hardware and software
environment, also called a platform, that ensures connectivity and easy
integration of future systems, including in-house software and
commercial packages. An analyst must determine exactly what the
organization wants to do. (Read more on the vle)
Initial and total cost of ownership (TCO)

• Evidently there will be some direct cost and indirect costs involved in
developing any information system. The TCO includes tangible
purchases of items, fees to be paid for services, and contracts called
hard costs. There are also additional soft or intangible costs of
management, support, training, and downtime costs which are more
difficult to measure. So there will always be that initial cost and
subsequent costs of acquiring any information system, to determine
which solution is optimum, the analyst must e able to determine the
toral cost of each alternative.
Scalability

• As explained below. Please refer there


Web integration

• An information system includes applications, which are programs that handle


the input, manage the processing logic, and provide the required output. The
systems analyst must know if a new application will be part of an e-commerce
strategy and the degree of integration with other Web-based components
• Web-centric architecture follows Internet design protocols and enables a
company to integrate the new application into its e-commerce strategy. Even
where e-commerce is not involved, a Web-centric application can run on the
Internet or a company intranet or extranet. A Web-based application avoids
many of the connectivity and compatibility problems that typically arise when
different hardware environments are involved. In a Web-based environment, a
firm’s external business partners can use standard Web browsers to import and
export data.
Legacy system interface requirements

• A new system might have to interface with one or more legacy


systems, which are older systems that use outdated technology, but
still are functional
• Interfacing a new system with a legacy system involves analysis of
data formats and compatibility. In some cases, a company will need to
convert legacy file data, which can be an expensive and time-
consuming process. Middleware might be needed to pass data between
new systems and legacy systems. To select the best architecture, the
analyst must know if the new application eventually will replace the
legacy system
Processing options

• In planning the architecture, designers also must consider how the


system will process data — online or in batches. A high-capacity
transaction processing system, such as an order entry system, requires
more network, processing, and data storage resources than a monthly
billing system that handles data in batches. Also, if the system must
operate online, 24 hours a day and seven days a week (24/7), provision
must be made for backup and speedy recovery in the event of system
failure. An analyst needs to be clear exactly which option the
organization prefers,
Security issues

• Aside password protection, and complex intrusion detection systems, security


threats and defenses are a major concern to systems analysts. As physical
designs are translated into specific hardware and software, analysts need to
consider security issues and determine how they will be addressed.
• Security is important when data or processing is performed at remote
locations, rather than at a centralized facility.
• In mission-critical systems, security issues have a major impact on system
architecture and design.
• Web-based systems often come with additional security concerns, as critical
data must be protected in the Internet environment. Firms that use e-commerce
applications must assure customers that their personal data is safe and secure
SCALABILITY
What is scalability?
• Scalability, also called extensibility, refers to a system’s ability to
expand, change, or downsize easily to meet the changing needs of a
business enterprise. Scalability is especially important in
implementing systems that are volume-related, such as transaction
processing systems.

• A scalable system is necessary to support a dynamic, growing business


SYSTEMS
DOCUMENTATION
Types of Systems Documentation
• Program Documentation
• System Documentation
• User Documentation
• Operations Documentation
Program Documentation

• Program documentation - describes the inputs, outputs, and processing


logic for all program modules. The program documentation process
starts in the systems analysis phase and continues during systems
implementation
• System analysts prepare overall documentation, such as process
descriptions and report layouts, early in the SDLC. This
documentation guides programmers, who construct modules that are
well supported by internal and external comments and descriptions
that can be understood and maintained easily. A systems analyst
usually verifies that program documentation is complete and accurate
System Documentation

• System documentation :
• Describes the system’s functions and how they are implemented. System
documentation includes data dictionary entries, data flow diagrams, object
models, screen layouts, source documents, and the systems request that
initiated the project. System documentation is necessary reference material for
the programmers and analysts who must support and maintain the system
User Documentation

• User documentation - consists of instructions and information to users


who will interact with the system and includes user manuals, Help
screens, and tutorials. While programmers or systems analysts usually
create program documentation and system documentation. To produce
effective and clear user documentation, someone with expert skills in
this area doing the development is required. User documentation
requires specialized skills, and competent technical writers as part of
the IT team
Operations Documentation
Operations documentation - contains all the information needed for
processing and distributing online and printed output. Typical operations
documentation includes the following information:
• Program, systems analyst, programmer, and system identification
• Scheduling information for printed output, such as report run
frequency and deadlines
• Input files and where they originate; and output files and destinations
• E-mail and report distribution lists
• Special forms required, including online forms
• Error and informational messages to operators and restart procedures
• Special instructions, such as security requirements
SYSTEMS TESTING
Types of Systems Testing
• Unit Testing
• Integration testing
• Systems Testing
Unit Testing
• Unit testing is the testing of an individual program or module. The
objective is to identify and eliminate execution errors that could
cause the program to terminate abnormally, and logic errors that
could have been missed during desk checking. Test data should
contain both correct data and erroneous data and should test all
possible situations that could occur. During unit testing,
programmers must test programs that interact with other programs
and files individually, before they are integrated into the system
Integration Testing
• Integration testing is the testing of two or more programs that depend
on each. It is also known as link testing. The output from the
validation program becomes input to the master file update program.
Testing the programs independently does not guarantee that the data
passed between them is correct. Only by performing integration
testing for this pair of programs can you make sure that the programs
work together properly
System Testing
• System testing is the testing of the entire system. A system test
includes all typical processing situations and is intended to assure
users, developers, and managers that the program meets all
specifications and that all necessary features have been included.
During a system test, users enter data, including samples of actual, or
live, data, perform queries, and produce reports to simulate actual
operating conditions. All processing options and outputs are verified
by users and the IT project development team to ensure that the
system functions correctly.
THANK YOU

You might also like