Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
PBL SESSION 1
Transcript of PBL SESSION 1
Question 1 (a)
Question 1 (b)
Question 1 (c)
Major subsystems in RBBH are:
Inventory control system
Customer ordering system
Management reporting system
Systems Development Life Cycle (SDLC) represents a process for creating or altering information systems, and the models and ways that people use to develop these systems
Represents initial investigation.
A brief study of the problem.
Defines the problem to be solved and sets the direction.
Specifies goal, scope, and resources.
Encik Bakar should identify the problems with the inventory control, customer ordering, and management reporting systems then set the solutions he desires.
Detailed understanding of important features of the system.
Develop analysis plan, gather facts, and analyze gathered facts.
Encik Bakar must gather more information on other alternatives available and analyze the data for system requirements then document the existing system.
Input, output, user interface, database, network, program, and control.
Encik Bakar have to define the requirements for detailed systems design and physically design the new system.
Construction and Implementation
System being developed.
Individual systems components are built.
Changes are written and tested.
Components built are put into operational use.
Encik Bakar must test the program codes that are written out, train his employees, prepare sites, convert to new system, and conduct post review.
Eliminate errors and fine-tune the system.
Plan for resource availability in carrying out these functions.
Implies continuous improvement.
Encik Bakar should perform corrective maintenance for any errors.
General System Theory is an outline in assisting an organizations to identify critical aspects of their environment.
A system have inputs, outputs, transformation process, exist in an environment, boundaries, and feedbacks.
Input is the energy and raw materials transformed by the system.
The inputs for RBBH is employee, information, energy, time, and raw materials for the burger.
Output is the product or service which results from the processing.
The output for RBBH is burgers.
Anything that is outside of the organization can be considered its environment.
Environment that is possible for RBBH is customers, suppliers, competitors, demographics, and tecnology.
Boundary is a line or point where systems can be differentiated from is environment .
Boundary for RBBH is vegetarian customers.
Feedback is the information that can be used to evaluate and monitor the system and to guide it to more effective performance.
Feedback for RBBH is sales report, customer satisfaction surveys, and how many burgers was wrongly made?
we will find out the detailed of the existing operations and the requirement for the new system
The project team investigates any current system(s), identifies improvement opportunities and develops a concept for the new system
answers the questions of who will use the system, what the system will do, and where and when it will be used
Analysis strategy, requirements gathering, system proposal
Many users want to create a new system but does not want to understand it. If we just build system in a way seems to be quick and easy we might have a weak system and faces with many problems that will arise later.
System Analysis- Determining Requirements
Question 1 (d)
information needs and system requirement proposed will be studied in more detail. The input, output, user interface, database, network, process and controls will be defined and documented.
In this phase, it decide how the system will operate, in terms of the hardware,software and network infrastructure, the user interface, forms and reports that will be used and specific programs, databases and files that will be needed
Design strategy,architecture design,database and file specifications, programs design
Can reduce the cost (manpower)
Can make the operation becoming more faster
Can help the management to manage the business
Can generate higher sales
Can help to conduct research and development and lower the associated cost
Implementation cost is high
Existence of Computer crime
The employer and employees need to be trained
OTHER FEASIBILITY STUDIES
Completion Date of the Project
If the project commence on 1st October 2013, the project target completion date is on 20th June 2014.
If Activity No. 6 were revised to take six weeks (42 days) instead of one week, the completion date will not be changed.
The other tasks (Activity No. 3,5,6 & 8) can each run over time before affecting the end date of the project
The amount of time a task can be extended before it effects other tasks is called ‘slack’ or ‘float’
Definition: the sequence of tasks from beginning to end that takes the longest time to complete
It is also the shortest possible time to complete
Any task in the critical path is called a critical task
No critical task can have its duration changed without affecting the end date of the project
Length of critical path is the sum of the lengths of all critical tasks
From the Gantt Chart (the red tasks) :
Critical tasks (Activity No. 1,2,4,7,9 & 10)
Therefore, length of critical path: (14 days+ 21 days + 49 days + 35 days + 56 days +14 days = 189 days)
The minimum amount of time required to get all tasks completed is 189 days
Prototyping is an approach in which a version of the proposed system is built rapidly and modified again and again based on the user’s reaction as they try out the prototype.