Wednesday, 22 February 2017

LESSON-3 COMPONENTS OF BUSINESS SYSTEMS (Cont’d; Ashraf, Khan, and Mir) Posted on September 21, 2012


LESSON-3 COMPONENTS OF BUSINESS SYSTEMS (Cont’d; Ashraf, Khan, and Mir)

LESSON-3 COMPONENTS OF BUSINESS SYSTEMS (Cont’d; Ashraf, Khan, and Mir)

 3. Software Construction By Parts

3.1 Overview

The object technology provides the application system construction from part by means of fabrication, customization, and assembly. These parts (objects, classes, or sets of classes and relationships) are modular application components, with well-defined interfaces and methods encapsulating data structures including generators, languages, and knowledge bases, and object oriented tools.

Language level: class libraries, which are the basic constructs provided with an object languages.

System Level: classes are organized in frameworks supporting; database access or client/server computing.

Industry and Business Level: For an industry oriented set of applications some general models template leading to Enterprise Resource Planning (ERP).

Enterprise Level: class libraries together with an enterprise model can reflect the specific characteristics and the requirement of the enterprise.

3.2 Application Development Environment

The normal phases of development of an application;

  • Requirements

  • Analysis

  • Design

  • Implement/ Produce

  • Build/ Testing

  • Production/ Maintenance.

The cross-life-cycle tools: The tools and services that span all development life cycle functions.

The life cycle functions include process and management, documentation, and reuse.

The application development platform (ADP) provides the means of the integration and storage area for all information pertaining to the enterprise, its development processes, application data, and the application.

The ADP components include; workstation services, library services, repository services, etc

The tools required for different phases:

Requirement, Analysis and Design Tools use the Enterprise Modeling Tools.

Analysis and Design Tools would be used mainly on Analysis and Design phase.

Languages, Generators, Knowledge Based System would be used mainly in implement and produce phase.

Test Maintenance/ Redevelopment Tools would be used

Requirements;

Definitions and Description of the Problem Domain (by questioning What?)

This involves the process of modeling a business enterprise for its present and future business structure and functions (mine by questioning How?)

This is to render the enterprise as viewed by senior management. This static model can further be added by dynamic enterprise simulation.

This planning stage furnishes context to probe further technical analysis and design work.

The tools used in structured enterprise modeling produce outputs such as;

  • Functional and process decomposition diagram

  • Logical data models

  • Usage and responsibility matrices

  • Property description

The Business functions are further broken down into the constituent Business processes, and down to the level of their specific business tasks step-by-step, which are pertinently stated.  Process decomposition diagram usually have same format as functional decomposition diagrams.

Logical Data Model: In a similar fashion as above, the conceptual information model is transformed into a logical data model to establish the data needs of the problem domain. Almost no rules exist about what can be a conceptual entity. It depicts the detail views of the data that application will require.

If one thinks an entity helps tell the story, and can give it a descriptive definition, can generally use it as a conceptual entity. These are directly translated into tables, but if the concept is important, a conceptual entity will still be represented by a collection of attributes contained within a table for another entity.

Conceptual entities don’t often have further characteristics (attributes) associated with them and are mostly used as communication tools for semantic purposes to learn about the major concepts to be analyzed further.

Conceptual entities with relationship names

Logical Entities

Logical entities include attributes to ensure fully understand how these entities are being used. But don’t necessarily use this model to communicate a physical design. So what constitutes an entity is entirely dependent upon the business process system being modeled. FK an instancedefined by an entity correlates roughly to a row or record in a table, in the same way that an entity correlates to a table.

                               Logical Entities 

Usage and Responsibility Matrices

These are constructed to show the relationships among processes, entities, business goals, critical successes factors and other relevant output at the planning stage.

Property Description

This contains information about processes, entities and other output from the planning stages.

Requirements Gathering

This transcribes business;  processes, information, (data), and business rules.

The classical Structural Analysis represents models of different aspects of business applications, such as entity-relationship (E-R), decomposition, relationship databases, and data flow diagrams.

Objects correspond to objects in the real-world, and behavioral component, defined by a set of procedures (methods) that allow access data and interaction with other objects.

Design


This phase specifies the computer related aspects of the application, such as screen designs, report designs, logical and physical database structures, data views for application programs, pseudo codes, mini-specifications for program modules, subsystem definitions.

On this prototyping or simulation techniques can be used to refine these aspects in collaboration with users/ experts.

Database Design

The design of physical database can proceed in parallel with application design.

In the design certain operational details are added; such as each expected volumes of each entity, update frequency rate, accesses over a given time-period, usage statistics, and external design specifications; technical considerations and constraints related to the implementation.

Implement/ Produce

The output from the analysis and design phase must be transformed into the input required to build an application.

Developers must also consider environmental details such as:

  • Security requirements

  • Recovery strategies

  • Documentation standards

  • Testing schedules

  • Scripts

The parts of the code are automatically generated, and the parts to be manually programmed.

Code Generators: The code generated is usually based on a transactional paradigm, which uses a transaction manager to provide communication support.

Knowledge Processing: This capability of doing a task derives from the knowledge about the task domain.

This knowledge can be represented in several paradigms; (if-then rules), frames, and prototypical description of objects.

The tools to process knowledge include expert tools and languages.

Expert Tools: These provide facility to store knowledge and then employ inference modules for problem solving based on the stored knowledge.

Fifth generation languages provide these processing to perform deduction by theorem proving, such as Prolog, knowledge databases, and logical predicates.

Languages: the traditional third generation languages, such as C, C++, PL/1, GUI, Java used for building object-oriented applications.

Building and Testing

This phase is done to integrate new function into the existing application set.

The actual activities depend on the characteristics of the application’s operating environment and the procedures defined for each installation.

 Production and Maintenance

When an application goes into real-life production, the application would be integrated with the rest of the applications, as well as for running in parallel, before cut over.

For then on, it is reasonable to accommodate business changes, add enhancement, or fix problems.

These are called maintenance activities through a number of mechanisms, including;

  • Redevelopment tools and techniques

  • Impact-analysis tools

  • Build, release, and control facilities

******

Click To MAIN PAGE: OBJECT- ORIENTED RELATIONAL MODELLING E-MONOGRAPH, By J. Ashraf, M. Khan, and H. Mir

Click to NEXT: LESSON-4 SOFTWARE CONSTRUCTION BY PARTS (Cont’d; Ashraf, Khan, and Mir)

*****

 MESSAGE: DEDICATED TO ANONYMOUS COMBATANTS OF KNOWLEDGE
مکتب علم الل مہد منل لحد   Learning continues from birth to death

FOR PROMOTION OF LEARNEDNESS SHARE WITH FRIENDS ABOUT;
   
  1. CAUSE AND EVENTS – SPATIAL And TEMPORAL RESPECTIVELY:                         https://be4gen.wordpress.com/2012/11/16/cause-and-events-spatial-temporal-respectively/

  1. WHETHER ‘BRAIN-POWER’ OR ‘HEART-IMPULSE’ PLINTHS ‘HUMAN GEN’? http://sunedu.wordpress.com/2012/09/17/whether-brain-power-or-heart-impulse-plinths-human-gen/

************

No comments:

Post a Comment