Professional Documents
Culture Documents
A Sad Discussion Handouts
A Sad Discussion Handouts
Importance of Research
In an Educational Institution
1. Institution
2. Community Extension
3. Research and Development
1. intellectually curios
2. prudent
3. accepts healthy criticism
4. honest
5. works well with others
6. updated
Every person who has the intellect and willingness to help solve
day-to-day problems of life: personal, family, local, national or
international in scope.
1. objectives: S-M-A-R-T
2. 5Ms: manpower, materials methods, money, market
3. selection:
personal interest and inclination
scientific merit
utility and uniqueness
cost
availability of qualified advisers and technologies
Sources:
books
journals
theses and dissertations
unpublished materials: documents
photographs
relics and old articles
Look for:
arguments
3
controversies
unclear findings
verifiable data
recommendations
1. Problem/Objectives
2. Theoretical/Conceptual Framework
3. Hypothesis
4. Research Design
Types
A. Historical – occurrences and development and
experiences about the past
B. Descriptive – deals with the present status of a
situation; leads to the conduct of other studies (i.e.
experimental)
- case study, survey, content analysis,
trend analysis, feasibility study, correlation
study; done in various settings
8. Conclusions/Recommendations
Elements of a System
System Fundamentals
1. Catalyst
2. Advisor
3. Educator
4. Salesman
5. Communicator
1. Knowledge
2. Education
3. Experience
4. Attributes
Types of System
1. Greater Efficiency
2. Maximizing profits
3. Resources used to the best advantage
4. Reduction of human effort
5. Faster turnaround
6. Reducing or eliminating errors in data and information
7. Consistent operations and procedures
8
1. Project Management
2. Forecasting Simulation
3. Sales and Marketing of good and services
4. Planning the orderly flow of information throughout an entire
business enterprise
5. Modifying or redesigning existing business system
6. System implementation
7. Computer programming and Utilization
8. Database Design
9. Forms design and management
10. Establishing system policies and procedures
11. Employment and training of organization personnel
12. Work measurement
13. Work simplification
14. Office layout
15. Selection and specification of office and information
processing equipment and supplies
16. Planning and designing internal and external
communication
TECHNICAL FESIBILITY
ECONOMIC FEASIBILTIY
OPERATIONAL FEASIBILITY
1. Time
2. Change
3. Staff
1. Feasibility
2. Investigation
3. Design
4. Implementation
4. The equipment
1. Problem Definition
2. Turning the alternative strategies into an outline computer based
system
3. Evaluating the outline computer based system
1. Technical Aspect
2. Operational Aspect
3. Economic Aspect
Feasibility Report
Investigation
1. Scope
2. Objective
3. Constraint
4. Resources of the investigation
11
Investigation Method
1. Interview Method
2. Questionnaires
3. Observation
4. Searching through records
Questionnaire
1. Should be very carefully designed
2. Should be explicitly defined and explained
3. Should be carefully chosen
4. Should be phrased very precisely
5. Should always have space for the recipient to answer
6. Time period should always carefully designed
7. Timing
8. Follow-up
PROJECT PLANNING
PROJECT SCHEDULE
Customers Questions
Deliverables
Documents
Demonstrations of functions
Demonstrations of subsystem
Demonstration of accuracy
Demonstration of reliability, security, or speed
Project Role
1. Requirement Analysis
2. System Design
3. Program Design
4. Program Implementation
5. Testing
6. Training
7. Maintenance
8. Quality Assurance
13
Personnel Characteristics
Types of Cost
1. Facilities
2. People
3. Project method and Tools
Project Plan
1. Project Scope
2. Project Schedule
3. Project Team Organization
4. Technical Description of the Proposed System
5. Project standards, procedures and proposed methodologies
6. Quality assurance plan
7. Special development tools and techniques
8. Configuration management plan
9. Documentation plan
10. Data management plan
11. Resource management plan
12. Test plan
13. Training plan
14. Security plan
15. Maintenance plan
REQUIREMENTS ANALYSIS
Requirement
What is the problem?
Analysis
CONFIGURATION MANAGEMENT
DEFINITION SPECIFICATION
Customer System
Designer
Types of Requirements
Physical Environment:
Where is the equipment to function?
Is there one location or several?
Are there any environmental restrictions, such as
temperature, humidity, or magnetic interference?
Interfaces:
Functionality:
17
Documentation:
For both input and output, what should the format of the
data be?
How often will it be received or sent?
How accurate must it be?
To what degree of precision must the calculation be made?
How much data flows through the system?
Must any data be retained for any period of time?
Resources:
Security:
Quality Assurance:
18
CHARACTERISTICS OF REQUIREMENTS
Requirements Validation
SYSTEM DESIGN
“How” “What”
TECHNICAL CONCEP
DESIGN TUAL
DESIGN
Form Function
20
Conceptual Technical
Design Design
Network topology
Protocol used
prescribed baud rate
21
Technical Description
PROGRAM DESIGN
1. Detailed Algorithms
2. Data Representations and Structures
3. Relationships among the functions performed and the data used
Design Guidelines
1. Top-Down Approach
2. Bottom-up Approach
4. Examination of Algorithms
5. Correctness of Algorithm
6. Efficiency of Algorithms
1. Reproducibility of results
2. Accuracy of results
3. Efficient expenditures of time and effort
4. Plan of action
5. Transferability of results
Recognize
Problem &
Identify Causes
Express Problem in
Quantitative Terms
Implement
the
Solution
Evaluate Results
and
Optimize
27
BEGI
N
Planning Phase
Analysis Phase
28
Design Phase
Development Phase
Implement-ation
Phase
END
GANTT CHART
DECISION TREE
FLOWCHART
2 Types of Flowchart
DATA DICTIONARY
Data Hierarchy
DFD Symbols
2. Select either the Gane and Sarson or Yourdon notation and used
them consistently.
5. Name and label all symbols and connectors. Select names that
are descriptive and reflect what is being done. Place text within
each symbol describing the function or transformation takes
place. Place textual labels next to flow lines or pipes to describe
the movements or transformation of data taking place.
7. Desk checks all data flow diagrams to make sure each symbols is
logically connected to another and that all symbols properly
describe the flow within the system.
8. Label the top of each data flow diagram with the system name,
date prepared, name of preparer, and other pertinent
information. This will be helpful when you or others refer to the
diagram later.