Malaysian Telecommunication Services Bhd

Published Date: 02 Nov 2017

This project is about the inventory system for Malaysian Telecommunication Services BHD. Basically inventory system is critically important for a business company because mostly deals with physical goods. For this inventory system, it will have enough inventories on hand in order to fulfill customer needs while investing lesser money on the inventory. The inventory system that will be proposed below will cover about how does Malaysian Telecommunication Services BHD controls their inventories systematically rather than go through manually. The inventory system will be accessed by both sales men and suppliers but there will be certain levels of access. Suppliers will be allowed to access the system only on the part regards to inventories needed to be supplied. Meanwhile, for the top management will be have total access to all levels of the system. The inventory system will be no manual work in the system, everything will be automated system.

Project objectives

The main objective of the inventory system will be the fully automated system of the inventories of Malaysian Telecommunication Service BHD in order to prevent errors to encounter in the business before the establishment of the inventory system.

The inventory system impartially will replace human intervention in the controlling of inventories manually which has been thought to be the first cause of mistakes encountered in the business.

Inventory system will provide a wide range of communication between Malaysian Telecommunication Service BHD employees and suppliers in order to keep all parties involved up-to-date of their business.

Inventory system will always update their sales records and in coming supplies in order to monitor the outgoing and incoming products. It also will help the people in- charge to know what is needed to be and provide any delays and losses.

Goal of the inventory system

The goal of the inventory system is to be the best Malaysian Telecommunication Services BHD system to assemble business efficiency and meet customers’ expectations.

Mission

Customer always right.

Reduce delays and mistakes in order to save time lesser costs. Therefore, the profit will increase.

Providing best services with professional training to enhance in time communications between Malaysian Telecommunication Service BHD.

Selection of Methodology

Structured Systems Analysis and Design Method (SSADM) is a systems approach to the analysis and design of information systems. It also can be an information systems development methodology.

SSADM divides an application development project into modules, stages, steps, and tasks, and provides a structure for describing projects in a way suited to manage the project. SSADM's objectives are to:

Improve project management and control.

Make more effectiveness the use of experienced and inexperienced development staff.

Develop better quality systems.

Establish a better structure for good communications between participants in a project.

SSADM cover up all the aspects of the life-cycle of a system from the feasibility study stage to the invention of a physical design; it is usually used in combination with other methods, which is concerned with the broader aspects of project management.

Besides that, SSADM sets out a flow or waterfall view of systems development, in which there are a series of steps, each of which leads to the next step. SSADM's steps, or stages, are:

Feasibility

Investigation of the current environment

Business systems options

Definition of requirements

Technical system options

Logical design

Physical design

The stages of SSADM include:

Stage 0: Feasibility

The Feasibility stage is a short assessment of a proposed information system to determine if the system can meet the business requirements of an organization, assuming the business case exists for developing the system. The analyst considers possible problems faced by the organization and produces various options to resolve these issues. Either the organization or you must decide if the costs of resolving the problems are worth the likely benefit to the project.

Stage 1: Investigation of the Current Environment

Detailed requirements are collected and business models are built in the Investigation of the Current Environment stage. This stage is where you develop a business-activity model, investigate and define requirements, investigate current processing in the data flow model, investigate current data and derive the logical view of current services.

Stage 2: Business System Options

The Business Systems Options, or BSO, stage allows the analyst and you to choose between a numbers of business-system options that each describe the scope and functionality provided by a particular development and implementation approach. After you present these to management, the management then decides which BSO is the better option.

Stage 3: Definition of Requirements

This stage specifies the details in the processing and data requirements of the selected BSO option. In this stage you define the required system processing, develop the required data model, determine the systems for existing or new functions, develop the user job specifications, enhance the required data model, develop specific prototypes and confirm the system objectives.

Stage 4: Technical Systems Options

This stage allows you and the analyst to consider the technical options. A detail such as the terms of cost, performance and impact on the organization is determined. You identify, define and select the possible technical system option in this stage.

Stage 5: Logical Design

This stage involves you specifying the new system through designing the menu structure and dialogues of the required system. The steps in this stage include defining the user dialogue, defining update processes and defining the inquiry processes.

Stage 6: Physical Design

This is the implementation phase of SSADM. The Physical Design stage is used to specify the physical data and process design use the language and features of the chosen environment and incorporate installation standards. This stage concentrates on the environment in which the new system will be running.

For each stage of SSADM, it sets out a sequence of techniques and procedures, and conventions for recording and communication between information pertaining to it. Both of it is in textual and diagrammatic form. SSADM is a very complete model, and a feature of the method is that projects may use only those elements of SSADM appropriate to the project. SSADM is supported by a number of CASE (computer aided software engineering) tool providers.

Waterfalls Life Cycle Model

SSADM follows the waterfalls Life Cycle Model which start with Feasibility study to physical design stage of development and the main feature with the involvement of the user in analysis stage. The techniques that SSADM used are logical data modelling, data flow modelling and entity behaviour modelling.

C:\Users\Alex\Desktop\pic001.jpg

Logical Data Modelling - This is the process of identifying, modelling and documenting the data as a part of system requirements gathering. The data will be separated into entities and relationships.

Data Flow Modelling – This is the process of identifying, modelling and documenting how data moves around an information system. Data Flow modelling examines processes, external entities of a system or receives data from a system and data flows.

Entity Behaviour Modelling - The process of identifying, modelling and documenting the events will affect each entity and the sequence in which these events occur.

Important characteristics of SSADM are:

Dividing a project into small modules with well-defined objectives

Useful during requirements specification and system design stage

Diagrammatic representation and other useful modelling techniques

Simple and easily understood by clients and developers

Performing activities in a sequence

Benefits of SSADM

The following is a list of benefits gained from using SSADM. The approach SSADM takes to make these benefits achievable are also described.

Deliver the system to users on time

Timeliness depends on two things:

Good planning

Good management and control.

SSADM has a modular structure which relates directly to project deliverables and helps in all aspects of project management. It gives a clear specification of what is to be produced and how it is to be managed and reviewed. There are well defined interfaces to management and specialist techniques.

Deliver systems that meets user's needs

By continuously involving users, by modelling business activities and work practice, by using prototyping, by making the IT professional's thinking visible through diagrammatic techniques, SSADM enhances the prospects for success on large and small projects.

Deliver systems which respond to changes in the business environment

SSADM helps in several ways here. Business Activity Modelling and Work Practice Modelling ensure that the focus of the project is on what the business requires. The system documentation produced makes visible:

Business objectives;

Practitioners’ thinking and understanding of the business objectives;

The link between the needs of the business and the system under development;

A precise specification for the design, building, maintenance and enhancement of applications.

SSADM precisely describes what has been captured in an advanced application development environments include 3GL, 4GL, Client Server, distributed systems, and many more.

Improve the effective and economic use of the skill available

SSADM uses the most commonly available skill in a wide market place - for example, Data Flow Modelling, Logical Data Modelling and Jackson-like structure diagramming. It promotes their effective use by aiding forward planning, and building up the skills base in the organization and on particular projects.

Improve quality by reducing error rates

Quality can be improved by detecting errors early in the lifecycle, especially by involving users as well as skilled practitioners in checking for errors. Rigorous techniques promote accuracy, with adequate checks of completeness and consistency. By defining the required quality of design documents, and stating the tests for them, SSADM promotes better quality management.

Improve flexibility

Every application development is different. The ability of tailoring SSADM to suit different projects is a major factor for organizations who wish to reuse their resource skills on other projects, and to be able to benefit from the many different ways in which SSADM techniques and products may be applied.

Improve productivity

Major boosts to productivity performance are achieved by:

Providing well documented techniques which accurately specify business and system requirements

Defining what is needed in automated support tools in support for SSADM's techniques

Using a product-oriented approach, avoiding the need to undertake unnecessary tasks, or to produce documentation at unnecessary levels of details

Using techniques to make thinking visible at each step; and

Promoting the specification of quality criteria.

Avoid lock-in to a single source of supply

The separation of logical system specification and physical design helps to establish a new layer of portability. It reduces the cost of re-implementing the system on new hardware and/or software.

Avoid IT developers’ administration

SSADM has been designed to provide useful tools for project managers and to transfer expertise to practitioners. Its use makes benefits, as well as costs, visible to both business and IT management and users.

Reference: (http://www.ogcio.gov.hk/en/infrastructure/methodology/ssadm/doc/s3a_pub.pdf)

Disadvantages of SSADM

It has a long development times because every stage must be completed before moving on to the next stage.

It costs time and money, Organizations must have large resources.

Lack of user contribution.

It is not flexible.

The main purpose of SSADM 

Function

A development of methodology offers the structured, detailed approach to information systems development. SSADM is a common approach for developing object-oriented applications that which has a graphical user interfaces. SSADM organize a project into small, well-defined tasks; identify the order of and relationship between the activities by way of diagrams and models. Unlike rapid function progression, or RAD, another common methodology which builds steps in parallel, SSADM defines each succeeding step on the outcome of prior steps.

Stages

SSADM consists of six stages. Following the feasibility study, sometimes referred to as "Stage 0," Stage 1 investigates the current systems environment. Stage 2 identifies business system options. Stage 3 analyzes and specifies functional requirements. Stage 4 describes the benefits, costs and constraints of technical system options. In Stage 5, developers describe how the system will process data and how users will interact with the system. Stage 6 is the physical design of the system and translates the logical design into real hardware and software at a very detailed and highly technological level.

Benefits

In addition to providing a means for improved project organization and self-documentation, SSADM also leads to reduced project costs due to higher quality analysis and system design, improved communication and increased staff effectiveness.

Reference: (Woodside, P. (1985) The Purpose of SSADM. [online] Available at: http://www.ehow.com/facts_7573075_purpose-ssadm.html [Accessed: 1 May 2013].)

Current System & Its Constrains

Malaysian telecommunication Service BHD, its current system is not fully systematic and the current system has no order to follow in other words its unsystematic. The business is running perfectly but not as efficiently as it could be due to it’s just a prototype but not a fully function program. The system requires time consuming because there is a lot of work and misunderstandings.

The system is time consuming because most of the work is done double. The inventories has to be sold and prepare another time to count how much was sold and how much is remaining which leads to mistakes and costly.

The current system does not meet customer’s expectations as the system. It leads to run out of inventories without notice, hence leading to customers failure meet their expectations.

Proposed System Opportunities

The proposed system will solve the entire problem stated above. The inventory system operations will be far away different from the current system simply because all the work will be automatically and systematically run.

There will be no much work. Besides that, there will be no much work force like in the current system. The proposed system will be self-updated showing the sold inventories and the remaining inventories in the store.

There will be minimal or even will be no mistakes in the inventory system like in the current system. Business run out of inventories and delays will not be bump into it anymore, because the system is able to show the remaining inventories and gives out a notice as a reminder to bring in supplies hence meeting customers’ expectations.

Overview of the Proposed System

Malaysian telecommunication Service BHD is looking forward to develop an objective inventory system. The system will be accessed by the company cashier and admin. Customers will have no access to the system simply because the system will not be online-based. The company will have suppliers even though with warehouse permission also won’t able to access into the system.

The proposed system will be fully automated with less involvement of human interaction and less paper work compared to the current system. Proposed system will be accessed as a stand-alone system. The system will be well developed good and friendly user interface.

The main objective of this system is to reduce the human interaction and what can be referring as manual work. Currently the system is running manually and everything is based on manual base, which leads to major errors which at times can lead to huge loss in the business.