1. In your own words, summarize the evolution of the information technology industry.
At first our IT industry was only used on important products and people could not afford using high-technology systems so they stick to manual procedures. But because some companies took the risk and use these high-technology systems and automated their production their time and efforts was not in vain. But because the companies that have not automated was being left behind by those who automated they did the same and created a chain reaction of spreading out automation until the present.
2. Why is it important to use systems analysis and design methodologies when building a system? Why not just build the system in whatever way seems to be "quick and easy"?
It is important to use system and analysis and design methodologies when building a system, because by we need to follow a standard, a standard, which was carefully studied and improved by the early programmers who were inline with system building. The methodologies of system analysis and design are important in many ways. One is for future use, if a system needs improvement and the maker of the system is no longer working in the company the programmer who is to improve the system will be able to understand the system.
3. Why is it necessary to have information systems in a organization?
Information system in an organization makes things faster and easier. With information system, exchange of information is faster and more accurate.
4. Interview at least (3) fourth year BSIT students and ask them to define the term system? From the three definitions make your own definition.
System
- Is a collection of interrelated parts or components that works together
for a common goal.
- Is composed of smaller groups or parts that act as one in order to perform
a specific task.
5 Define each of the ff. terms.
System - an organized set of related components established to perform a certain task.
Analysis - dividing the object into components or into
smaller
Information system - combination of hardware, software, people,
procedures and data.
Computer Application - A computer program with a user interface.
- A computer program designed for a specific task or use.
System Analyst - A person who plans and designs individual programs
and entire computer systems.
Information Technology - Integration of computing technology and
information processing.
Outsourcing - acquiring products or parts from an outside source.
Joint Application design - structured process in which users,
managers, and analysts work together for several days.
Prototyping - creating a limited working system or subset of a system
that will develop or test design concepts.
Participatory Design - A systems development approach that originated
in northern Europe in which users and the improvement in their work
lives are the central focus.
1. Describe why information is most usefully thought of as an organizational resource rather than as an organizational byproduct.
Information is most usually thought of as an organizational resource rather than as an organizational byproduct because it is used by the organization for productivity, we use information to improve the organization's performance, we also use information for strategic planning e.g. acquiring information regarding competitors would lead to the organizations planning on using this information as an advantage, we use information to know how to make a certain task, and we use information to know what changes will take place on the organization depending on what is happening outside it.
2. Contrast internal and external communication
Internal communication involves 2 or more people who are members of the organization while external communication involves two or more organizations
3. Contrast vertical and horizontal communication
Horizontal communication occurs between two or more persons of the same level while vertical communication happens between persons not of the same level in an organization.
4. What is meant by saying that organizational subsystems are interrelated and interdependent?
Organizational subsystems are interrelated and interdependent,
interrelated in the sense that they make up one large system which will function accordingly to other subsystems.
Organizational subsystems are interdependent in a way that a subsystem may need requirements like maybe user input or permission from the main system on which the other subsystem had acquired.
5. Research for the definition of the following key terms:
Communication - the transfer of information from a sender to a receiver through a media or medium
Formal Oraganization - group of people who work together to achieve a specific goal or set of goals
Organization Chart - a visual, graphic device that shows the lines of authority and chain of command in an organization
Line Organization - a classical structure resembling a pyramid, where relationships are shown by lines drawn on a chart
Committee Oraganization - a structure in which a position or responsibility is assigned to a group of individuals rather than to a single person
Cohesion - the extent to which system or a subsystem performs a single function
Coupling - the ectent to which the subsystems depend on each other
Open Systems - a system that interacts freely with its environment, taking input and returning output
Modularity -dividing a system into chunks or modules at a relatively uniform size
Interface - the place at which two independent systems meet and act on or communicate with each other
- point of contact where a system meets its environment or where subsystems meet each other
| Assignment # 1 | Download Assignment # 1 |
| Assignment # 2 | Download Assignment # 2 |
| Assignment # 3 | Download Assignment # 3 |
| Case # 1 | Download Case # 1 |
| Case # 2 | Download Case # 2 |
| Case # 3 | Download Case # 3 |
What systems concept did Richard and Harry ignore in tossing out the pink forms? What are the possible ramifications for systems analysts if general systems concepts are ignored?
Richard and Harry ignored the scheduling system that Carbon, Carbon and Rippy have. They were not even informed by Ms. McCue that the auditing process for those pink forms is done quarterly (every three months). On Richard�s two-month stay in the company, he never knew that the procedure is such. On the other hand, Richard should have investigated the company by observing the operations held. Two months may not be adequate for observing these operations because there are operations done quarterly, semi-annually, annually, and the like. Richard should have also investigated on what those pink forms are for by merely asking rather than immediately deciding on what to do with them, which even lead to a wrong procedure. Secondly, they ignored the security of the company's system. The pink forms were back-up files of the company and it also serve as a form for double checking.
The possible consequence of ignoring such procedures for systems analysts is that the currently existing systems may not be investigated on. According to Carol, those pick forms are audited to be compared to the computer stock purchase information for transaction accuracy. By doing so, systems analysts may know whether the existing system is effective on it�s accuracy or not. But because of what Richard did, the accuracy of the system currently existing may not be measured.
1. a. Make a basic list of dos and don'ts when developing DFD.
Do's:
Processes:
All processes should be named with a strong action verb followed by an object clause that describes what the work is performed on or for.
Essential processes include processes that:
Perform computations.
Make decisions.
Split data flows based on content or business rules.
Combine data flows.
Filter and/or summarize data flows to produce data flow(s).
Data Flows:
Essential data flows should represent the minimum essential data needed by the process that receives the data flow.
Data flow names should be nouns and noun phrases that are singular.
Data flow names should be unique (except for those to and from data stores).
All data flows must begin and/or end at a process, because data flows either initiate a process or result from a process.
Entities:
Entities should be named with descriptive nouns.
Data Stores:
There should be one data store for each data entity on your entity relationship diagram.
Data stores should be named after the data model or entities.
Names should be plural.
Use separate data flows for the use and the update.
Don'ts:
Processes:
Include processes that do nothing more than move or route data, thus leaving the data unchanged.
Include processes that have inputs but have no outputs (black hole).
Include processes that have outputs but have no inputs (miracles).
Include processes that have insufficient inputs to produce outputs (gray holes).
Data flows:
Use diverging data flow on essential DFDs.
Use data flow connecting entity to another entity, data store to another data store, or data store to an entity and vice versa.
Entities:
Naming entities using plural nouns (discouraged).
Using names instead of titles.
Data Stores:
Use or update data stores using entities or another data store.
b. Describe the rules for developing a context level diagram
In Developing a context level diagram it should show the main processes and data stores of the system.
c. Describe in simple terms what is leveling (explosion) and balancing.
Explosion / Leveling is the expounding of a process to be consisted of simple processes.
2. The group disagrees to the systems analyst's opinion. Structured Analysis using DFDs and Data Dictionaries is not too academic nor does it have too much new terminologies. Symbols used in this kind of Structured Analysis are too minimal that one would not be confused in identifying one symbol to another. Also, terminologies used are not too complicated. A symbol is actually termed exactly what it does in layman's term. The terminologies for the guidelines of using the different symbols are even very elementary such as "use action verb" and the like. These terminologies are not new to us.
Balancing is a process in which the data that are included in the diagram should still be there when explosion has taken place.
![]() |
|||
![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||
![]() |
|||