Enterprise Resource Planning (ERP)

From news article or internet information, find an example of an organization that is installing an ERP package. If possible get a copy of the over-all project plans and analyze the various activities and compare them with a standard SDLC.

This the article that discussed the implementation of ERD to Matsushita Communication Industrial Corporation of the Philippines (MCP), now Panasonic Mobile Communications Corporation of the Philippines.

Matsushita Communication Industrial Corporation of the Philippines

• Industries: Manufacturing
• Offering Groups: Solutions
• Solution Areas: Enterprise Resource Planning
• Regions: Philippines

The Matsushita Communication had a direction to standardize the operations of all its overseas companies through the implementation of an Enterprise Resource Planning (ERP) solution.

The company decided to use Glovia, an ERP solution that addresses the needs of the discrete manufacturing market, developed by Glovia International. Glovia defined their global standards in production planning, production, and inventory control systems. The project was successfully completed in 4.5 months and with the outstanding performance of the Fujitsu Philippines team in this activity, MCI decided to partner with the company in all other Matsushita implementations around the globe.

The article does not discuss the overall project plans it only discusses the phase of the implementation was focused on the cellular phone business of the Overseas Mobile Telephone Division (OMTD). This also led to the development of specific add-on functions, which were done by Fujitsu Japan.

Enterprise Resource Planning (ERP)

In this assignment we would know all about ERP-its advantages and disadvantages that can be made to the organization and companies that installing this package.

ERP

ERP is Enterprise Resource Planning. It is the present evolution of manufacturing resources planning systems. ERP provides the foundation for integrating enterprise-wide information systems. These systems will link all aspects of a company's operations including human resources, financial planning, manufacturing, and distribution, as well as connect the organization to its customers and suppliers. Examples of ERP packages are HRMS, Financials, Manufacturing, Distribution, and Sales. Each ERP Package may offer different functionality for different industries. ERP (Enterprise Resource Planning) systems typically include the following characteristics: (1) An integrated system that operates in real time (or next to real time), without relying on periodic updates. (2) A common database, which supports all applications. (3) A consistent look and feel throughout each module. (4) Installation of the system without elaborate application/data integration by the Information Technology (IT) department. Advantages of an ERP system:

- Information entered once into system .

- Forces use of the best practices.

- Allows customization.

- Based on reliable file structure.

- Provides functionality to interact with other elements in the process.

- Provides tools for ad hoc queries.

And also according to ERP Software Solutions there are five major benefits of ERP:

• On-line/real time information throughout all the functional areas of an organization.
• Data standardization and accuracy across the enterprise.
• Best-practices or optimized solutions are included in the applications.
• Creates efficiencies that organizations would not otherwise have.
• The analysis and reporting that can be used for long-term planning.

In implementation, ERP systems include several basic features. They are installed on a Database Management System. Database platforms to choose from are: DB2/400, DB2/MVS, DB2/Unix, Informix, MS SQL Server, Oracle, SQLBase, and Sybase. They require initial setup according to the organization's process. They may be customized according to the organization's process through the ERP's tool set. Work flow can be setup to automate approval processes through chains of command. Once installed, the user only enters data at one point, and the information is transferred through processes to other modules. Finally, the ERP system includes reporting tools for main reports.

ERP and SDLC

There are many differences of Enterprise Resource Planning and System Development Life Cycle such as the in the ERP’s features. The ERD system is the foundation of the company-wide Integrated Information System, performing foundations corporate activities and increases customer service, belief that it is the only solution for better Project Management compared to the other planning tools, addressing not only the current requirements of the company but also providing the opportunity of continually improving and refining business processes and above all, providing business intelligence tools like Decision Support Systems (DSS), Executive Information System (EIS),Reporting and many more that can help the company in the decision making to improve its business process.

References:

http://en.wikipedia.org/wiki/Enterprise_resource_planning

http://www.fujitsu.com/ph/casestudies/matsushita.html

http://erp.cc/erpinfo.htm

ASSIGNMENT 11

You were tasked by the IC-dean to evaluate the enrollment system of the university, list and briefly describe the characteristics that an analyst (you) examines when choosing or defining deployment environment.

As an assignment I was tasked by the IC-dean to evaluate the enrollment system of the university. In evaluating the enrollment system of the university there are many things to consider in evaluating it. And one of the primary considerations in developing a new information system is the application deployment environment. As the definition says that deployment environment is a collection of configured clusters, servers, and middleware that collaborate to provide an environment to host software modules. An important part of any project is ensuring that the application deployment environment is defined and well matched to application requirements. At this life cycle stage, the analyst’s goal is to define the environment in sufficient detail to be able to choose from among competing alternatives and to provide sufficient information for design to begin.

These are the characteristics examines when choosing or defining deployment environment:

Consider the configuration
In this characteristic the Analyst must consider the configuration of computer equipment, the operating systems, and also the networks that will exist when the new application system is deployed.

Determine the constraints
The second one is that the analyst must determine the limitation that are imposed on the system development and its alternatives.

Define Environment
The third one is that the analyst must define its environment or its multiple environmental choices that can match the application requirements.

Define Application
The analyst must define the organization’s strategic application.

Define Plans
The analyst must define technology architecture plans.

Determining Alternatives
Prioritizing the requirements is determining what alternatives are possible for developing the solution.

In conclusion with this deployment environment choices, specifically with its operating system, the Database Management System, and also the distribution of the software in the case of its standardization, the tendency to limit the development tool choices. With this, the analyst should consider all the development and the development environments together when it comes in determining on fitting to a particular application.

Assinment 10: With reference to assignments 8 and 9, what characteristics does an analyst(you) examine when evalauating DFD quality? (1500 words)

As an introduction to the assignment ten, base on the assignment eight and nine we are task to make an UML Unified Modeling Diagram-different diagrams that can illustrate a process or system, in our case we are task to illustrate the pre-enrollment of University of Southeastern Philippines. In assignment eight we are task to develop an activity diagram and a fully developed description for a use case. Activity Diagrams are usually used to a business process model, for modeling the logic captured by a single use case of a business or a system, it is also for modeling the detailed logic of a business rule or the rules of the system how it works. Creating activity diagrams are very useful in describing the flow control of the target system. It is also helpful in determining the use cases and the business processes of a company or a system that a company may use. With the assignment nine we are task to create at least 3 different types of Data flow diagram of USEP's pre-enrollment system. First we defined what data flow diagram is all about. Data flow diagram is a graphical representation of data on how the process goes in the system or business. According to Scott W. Ambler data flow diagram shows the flow of the data from external entities into the system, how the data moved from one process to another as well as its logical storage. Data flow diagram can also be used for the visualization of data processing. A Data flow diagram provides no information about the timing of processes, or about whether processes will operate in sequence or in parallel. It is therefore quite different from a flowchart, which shows the flow of control through an algorithm, allowing a reader to determine what operations will be performed, in what order, and under what circumstances, but not what kinds of data will be input to and output from the system, nor where the data will come from and go to, nor where the data will be stored. Also according to Hoffer, George and Valacich there are two defined data flow diagrams, includes context diagram and level-O diagrams. To differentiate, context diagram is a data flow diagram (DFD) of the scope of an organizational system that shows the system boundaries external entities that interact with the system and the major information flows between the entities and the system. On the other hand, level-O diagram is a data flow diagram (DFD) that simply represents a system’s major processes, data flows and data stores at a high level detail.

The data flow diagram has a purpose and it provide the meaning between users and systems developers. And it diagrams are first graphical, eliminating thousands of words; second is logical representations, modeling WHAT a system does, rather than physical models showing HOW it does it; third is hierarchical, showing systems at any level of detail; and allow the user to understand review the process.

There are characteristics examined in evaluating the data flow diagram. First is Remember, also referred to as recognition or recall. Be able to remember or recognize terminologies, definitions, facts, ideas, materials, patterns, sequences, methodologies and principles. Second is to Understand. Will be able to read and understand descriptions, communications, reports, tables, diagrams, directions and regulations. Third is to Apply. Be able to apply the ideas, procedures, methods, formulas, principles, theories and to the related situation that can be apply on the diagram. Fourth is Analyze. To be able to break down information into its constituent parts and recognize the parts’ relationship to one another and how they are organized; understand the data’s from a complex process. The fifth one is to Evaluate. To be able to make judgments regarding the value of proposed ideas, solutions, methodologies, and many more by using the proper standards to estimate accuracy, effectiveness, economic benefits, and many more. The last one is to Create. Be able to identify which data or information from a complex set is appropriate to examine further or from which its supported conclusions can be drawn.

Data flow diagram has the following symbols: Process flow diagrams. It has the following entities, process number, where the activity is happening and its process name. Data flow datagram. It symbolizes the transformation of data, there must be data flowing into/out of the process, process can have several inputs to it or output to it and process with no out becomes a null process. Data store Symbol. Consist of the following entities, data store number and name of data store. The function of data store is to designate the storage of data in a DFD diagram. Rules of Data store-First rule is that the data flow diagram data store do not by level but they may reappear incase needed and secondly that the symbol and the numbering remain the same. Data flow symbol. Data flow symbol may appear in different shape and they signify the movement of data. They do not signify the movement of people, goods. Doubles an arrow signifies that activities occur at the same time which is wrong and Data flow in is never equal to data flow out. Extended entity symbol. Extended entity is sources and destination of data. This means that source is the origin and destination is the sink of data.

Dos and Don’ts of external entity
• External entity never communicate with each other, this signify that there is no need for the process
• External entity should not communicate directly with data store because external entities can be identifier with the record of files and databases

How to develop Logical data flow diagram

Below are the guidelines in developing data flow diagrams
1. Develop a physical DFD
2. Explore the process for more details
3. Maintain consistency between the process
4. Following meaningful leveling convention
5. Ensure that DFD diagrams clarifies what is happening in the system
6. Remember DFD audience
7. Add control on the lower level DFD only
8. Assign meaningful level
9. Evaluate DFD for correctness

Step in drawing DFD diagrams
1. Make a list of all business activities and use it to determine the various external entities, data flows, process and data store
2. Create a context diagram which shows external entity and data flows to and from the system
3. Do not show any detailed process or data store
4. Draw diagram zero or the next level to show process but keep them general. Show data stores and the level
5. Create a child diagram for each of the process in diagram zero
6. Check for errors and make sure the levels you assign to each process and data flow are meaningful
7. Develop a physical DFD diagram from the logical DFD and distinguish between the manual and automated protocol, describe actual files and report by name and controls to indicate when the process are complete or errors occurs
8. Portion the physical DFD by separating or grouping parts of the diagram in order to facilitate programming and implementation

Advantages of data flow diagrams
• It gives further understanding of the interestedness of the system and sub-systems
• It is useful from communicating current system knowledge to the user
• Used as part of the system documentation files
• Dataflow diagram helps to substantiate the logic underlining the dataflow of the organization
• It gives the summary of the system
• DFD is very easy to follow errors and it is also useful for quick reference to the development team for locating and controlling errors

Disadvantages of data flow diagram
• DFD is likely to take many alteration before agreement with the user
• Physical consideration are usually left out
• It is difficult to understand because it ambiguous to the user who have little or no knowledge.

Data Flow Diagram Principles

* The general principle in Data Flow Diagramming is that a system can be decomposed into subsystems, and subsystems can be decomposed into lower level subsystems, and so on.
* Each subsystem represents a process or activity in which data is processed. At the lowest level, processes can no longer be decomposed.
* Each 'process' (and from now on, by 'process' we mean subsystem and activity) in a DFD has the characteristics of a system.
* Just as a system must have input and output (if it is not dead), so a process must have input and output.
* Data enters the system from the environment; data flows between processes within the system; and data is produced as output from the system


1. A system can be decomposed into subsystems, and
subsystems can be further decomposed into lower level
subsystems.
2. Each subsystem represents a process or activity in which
data is processed.
3. At the lowest level, processes can no longer be decomposed.
4. Each 'process' has the characteristics of a system. A process
must have input and output.
5. Data enters the system from the environment, data flows
between processes within the system and data is produced
as output from the system.

General Data Flow Rules
1. Entities are either 'sources of' or 'sinks' for data input and outputs - i.e. they are the originators or terminators for data flows.
2. Data flows from Entities must flow into Processes
3. Data flows to Entities must come from Processes
4. Processes and Data Stores must have both inputs and outputs (What goes in must come out!)
5. Inputs to Data Stores only come from Processes.
6. Outputs from Data Stores only go to Processes.

Now, back to the main question, what characteristics does an analyst (you) examine when evaluating DFD quality? To be honest, I really had a hard time thinking of how to create good and perfect data flow diagrams. But with the guidelines above information that is mentioned I think I can evaluate A data flow diagram.

References:

http://hubpages.com/hub/What-is-a-data-flow-diagram

http://www.agilemodeling.com/artifacts/dataFlowDiagram.htm

http://www.asq.org/certification/quality-process-analyst/bok.html

http://www.cmp.jobs/qa-analyst-1153.php

http://spot.colorado.edu/~kozar/DFDtechnique.html