THE REQUIREMENT ANALYSIS AND SYSTEM DESIGN 

THE REQUIREMENT ANALYSIS AND SYSTEM DESIGN 

Object-oriented method and approach

The object-oriented (« 00 », for short) concept and approach have been used in many areas and for a myriad of applications, including software engineering, to name but one.
00 approaches are now specifically considered as a useful alternative to the traditional approaches. The traditional approach models scheduling problems from two different points of view, namely functional decomposition and related information (data-oriented).
The 00 approach, however, unifies functional decomposition with related information. Its principal aim is to blend together the functional approach and the data approach through the use of messages between objects; to divide real-world entities into classes and objects, et cetera; to represent classes and objects and their relationships and to describe the interconnectedness between abstraction and reality. The main advantages of the OO approach are realism, flexibility, re-usability and extensibility.
In this thesis, the design of the software is based on the principles of Object Oriented Programming (OOP). This allows for the development and testing of various parts of the code to be done independently. OOP also allows the code to be easily extended.

Java

Java is designed to meet the challenges of application development in the context of heterogeneous, network-wide distributed environments. Paramount among these challenges is secure delivery of applications that consume the minimum of system resources, can run on any hardware and software platform, and can be extended dynamically.
Java originated as part of a research project to develop advanced software for a wide variety of networked devices and embedded systems. The goal was to develop a small, reliable, portable, distributed, real-time operating environment. When the project started, C++ was the language of choice. But over time the difficulties encountered with C++ grew to the point where the problems could best be addressed by creating an entirely new language environment. Design and architecture decisions drew from a variety of languages such as Eiffel5 SmallTalk, Objective C, and Cedar/Mesa. The result is a language environment that has proven ideal for developing secure5 distributed, network-based end-user applications in environments ranging from networked-embedded devices to the World-Wide Web and the desktop.
The Java system that emerged to meet these needs is simple, so it can be easily programmed by most developers; familiar, so that current developers can easily learn Java; object oriented, to take advantage of modern software development methodologies and to fit into distributed client-server applications; multithreaded, for high performance in applications that need to perform multiple concurrent activities, such as multimedia; and interpreted, for maximum portability and dynamic capabilities.

Oracle

An Oracle database is a collection of data treated as a unit. The purpose of a database is to store and retrieve related information. A database server is the key to solving the problems of information management. In general, a server reliably manages a large amount of data in a multiuser environment so that many users can concurrently access the same data. All this is accomplished while delivering high performance. A database server also prevents unauthorized access and provides efficient solutions for failure recovery.
Oracle Database is the first database designed for enterprise grid computing, the most flexible and cost effective way to manage information and applications. Enterprise grid computing creates large pools of industry-standard, modular storage and servers. With this architecture, each new system can be rapidly provisioned from the pool of components.
There is no need for peak workloads, because capacity can be easily added or reallocated from the resource pools as needed.
The database has logical structures and physical structures. Because the physical and logical structures are separate, the physical storage of data can be managed without affecting the access to logical storage structures.

JBuilder

JBuilder is a programming compilation tool dedicated to Java which through it’s extensive Component Palette contains many of the pre-coded classes emanating from the original Java Language but in a « drag and drop format. Unlike some other Visual Programming tools, not only does it support the reuse of library classes, it retains the ability, at the lowest level, to be amended by the introduction of Java source code as a means of constructing bespoke packages.

THE DATA INPUT CLASS

The data input class will be addressed first because it gets all necessary data into memory from the database for the later use. The corresponding ‘ZRDatalnput class allows us to dynamically build all tables in memory. The default data source is database. It als llows the user to read the data from other data source specified in the configuration file.
This class contains all of the information needed to calculate the load of the work area.Each vector contains the records data of the corresponding table. It uses the base class of the record. For example, the Vector vMnfOrder uses the MnfOrderRecord class which is coiresponding with one record of the Manufacturing order table.
The following table shows the ZRDatalnput public fonction declarations. These fonctions are the users interface to the load calculation fonction.

LOAD CALCULATION CLASS

The ZRLoadCalcul class is the most important class in this module, because it performs not only the load calculation of the work area according to the measure unit, it also takes the task of auto-balance of the load. The load calculation is performed by using the work time of each manufacturing process deployed by the manufacturing order.
The auto-balance load fonction will process and reschedule all open and planned manufacturing orders using backward scheduling. Backward scheduling logic will calculate each operation backwards from the manufacturing order or planned order.

Table des matières

INTRODUCTION
CHAPTER 1 REVIEW THE EVOLUTION OF ERP 
CHAPTER 2 THE REQUIREMENT ANALYSIS AND SYSTEM DESIGN 
2.1 LOGIN FUNCTION
2.2 DATA INPUT FUNCTION
2.3 CALCULATE LOAD FUNCTION
2.4 AUTO-BALANCE FUNCTION
2.5 MANUAL ADJUST FUNCTION
2.6 CHECK THE FEASIBILITY OF THE PLANNING
2.7 OUTPUT THE NON-EXECUTABLE INFORMATION
2.8 DATA OUTPUT
2.9 LOGOUT
CHAPTER 3 THE CLASS DESCRIPTION 
3.1 THE UML OF THE CRP MODULE
3.2 THE DATA INPUT CLASS
3.3 LOAD CALCULATION CLASS
3.4 MANUAL ADJUST CLASSES
3.5 CRP TASK CLASS
CHAPTER 4 THE IMPLEMENTATION 
CONCLUSION

Télécharger le rapport complet