Anda di halaman 1dari 23

THESIS/SAD/SDD/IRM

PROJECT DOCUMENTATION FORMAT

I.

TITLE PAGE

TECHNOLOGICAL INSTITUTE OF THE PHILIPPINES Aurora Blvd., Quezon City {in bold characters, font size 16} <PROJECT TITLE> {in bold characters, underlined, font size 14} A Project Presented to Information Technology Education Department In Partial Fulfillment of the Requirements for -----{state the specific subject/course} by: <lastname, firstname, m.i. of the proponent 1> <lastname, firstname, m.i. of the proponent 2> <lastname, firstname, m.i. of the proponent 3>

<Date of Submission>

I.

ADVISERS RECOMMENDATION SHEET

TECHNOLOGICAL INSTITUTE OF THE PHILIPPINES Aurora Blvd., Quezon City {in bold characters, font size 16} ADVISERS RECOMMENDATION SHEET {in bold characters, underlined, font size 14} This Project Entitled <Project Title> {in bold characters, font size 14} by: <lastname, firstname, m.i. of the proponent 1> <lastname, firstname, m.i. of the proponent 2> <lastname, firstname, m.i. of the proponent 3> And Submitted in Partial Fulfillment of the Requirements of -----( state the specific subject/course ) has been Examined and is Recommended for Acceptance and Approval <Project Advisers Signature> <Project Advisers Name> <Adviser>

I.

PANELS APPROVAL SHEET

TECHNOLOGICAL INSTITUTE OF THE PHILIPPINES Aurora Blvd., Quezon City {in bold characters, font size 16} PANELS APPROVAL SHEET {in bold characters, underlined, font size 14} This Project Entitled <Project Title> {in bold characters, font size 14} by: <lastname, firstname, m.i. of the proponent 1> <lastname, firstname, m.i. of the proponent 2> <lastname, firstname, m.i. of the proponent 3>

after having been presented is hereby approved by the following members of the panel

<Panelist 1s Signature> Panelist

<Panelist 2s Signature> Panelist

<Lead Panelists Signature> Lead Panelist

II.

CHAIRS ACCEPTANCE SHEET

TECHNOLOGICAL INSTITUTE OF THE PHILIPPINES Aurora Blvd., Quezon City {in bold characters, font size 16}

CHAIRS ACCEPTANCE SHEET {in bold characters, underlined, font size 14} This Project Entitled <Project Title> {in bold characters, font size 14}

After having been Recommended and Approved is hereby Accepted by the Information Technology Education Department of Technological Institute of the Philippines Quezon City <Chairs Signature> <Chairs Name> Department Chair TABLE OF CONTENTS {in bold characters, font size 14} 1.0 INTRODUCTION 1.1 Background of the Study 11 1.2 Statement of the Problem 1 2. -------------------------------------7.0 LIST OF APPENDICES Appendix <Appendix number> TABLE OF CONTENTS <appendix caption>

1-1

III.

IV.

ACKNOWLEDGEMENT This section contains expressions of appreciation for assistance and guidance. This should be expressed SIMPLY and TACTFULLY and should fit into a single page only. See the attached sample for your reference.

V.

REVIEW OF RELATED STUDIES A. General Literature Survey (resources according to your major or area of study) B. Abstracts/Compiled Abstracts (crude source of materials) C. Trade Literature (national journals R&D trend in the country and information journals R&D at international level) D. Personal Interviews E. Evaluation of Existing Software / System. Example: A. General Literature Survey A.1 Computer Assisted Instruction

Computer Assisted Instruction (CAI) refers to the use of ---------------------------A.2 Intelligent Computer Aided Instruction --------------------------------------------VI. BIBLIOGRAPHY Citations, as they appear within the text, should be coded to reflect the first four characters of the principal authors last name suffixed by the year of publication. Thus, [WHITT2004] refers to the publication of Jeffrey Whitten for his work this year. BOOKS <CODE> <authors name>(<year of publication>).<Book Title> <site of publication>: <Complete name of Publisher>

Example: [WHIT2004] J. Whitten(2004). Systems Analysis and Design Methods. Burr Ridge, Illinois: Irwin, Inc. JOURNALS <CODE> authors name>(<year of publication>:<Article Title>, volume number issue number, <pages where articles are found>.

Example: [BAET1998] JCM Beaten & JA Bergstrat(1998) Global Renaming Operators in Concrete, Information and Computation, 78(3), pp205 245. CONFERENCE <CODE>

authors name> (<year of publication>).<Article Title>, in: Conference Name (editors of proceedings, ed), <pages were article could be found>. <site of publication>: <complete name of publisher>. DHE Park(1986). Concurrency and Automata on Infinite Sequences, In: Fifth GL Conference (P. Duessen, ed), pp. 167 183. Berlin:Springer-Verfag.

Example: [PARK1986]

WORLD WIDE WEB <CODE> <subject of the page>(year). Homepage Title. URL site

Example: [CRUZ1995]

J. Cruz(1995). Homepage of Juan Dela Cruz. http://tip.edu.ph. THESIS PROGRAM MAIN DOCUMENTATION OUTLINE

Title Page Advisers Recommendation Sheet Chairs Acceptance Sheet Panels Approval Sheet Table of Contents List of Appendices List of Tables List of Figures Acknowledgement 1.0 Introduction 1.1 Background of the Study 1.2 Statement of the Problem 1.3 Objectives of the Study 1.3.1 General Objective 1.3.2 Specific Objectives 1.4 Significance of the Study 1.5 Scope and Limitation Methodology of the Study Review of Related Studies Data Gathering Procedures and Output Documentation of Current System 5.1 Description of the Current System 5.2 Hardware Setup 5.3 Software and Application being used 5.4 Personnel Requirement Analysis Specification System Design Specification System Requirement Specification 8.1 Hardware Requirements 8.2 Software Requirements

2.0 3.0 4.0 5.0

6.0 7.0 8.0

8.3 9.0

Human Resource Requirements

Summary, Conclusion, and Recommendation

Appendices Bibliography Resource Person Personal Vitae THESIS PROGRAM MAIN DOCUMENTATION GUIDELINES 1.0 All Thesis Documentation should adhere to the following standards: a. Margins Left Right Top 1.5 1.0 1.0 b. Font 1. Text 2. Heading or Sub-headings c. Spacing d. Footer <Thesis Title> Line Text e. Pages Black, 1 pt. Times New Roman, size 11, Regular The page notation to be used is: <chapter/appendix letter page number> . Thus the first page for Chapter 2 is at 2-1, while the first page of Appendix A is at A-1. There should be no page numbers for items before Chapter 1. <Page> Font Times New Roman Times New Roman Size 12 12 Bold Font Style Regular *use Italics or single underline in emphasizing some text.

Bottom 1.0

Double Space

f. Sub-headings and text All text and sub-headings should be in the following format as shown by an example below: 2.0 REVIEW OF RELATED STUDIES

2.1 Computer Assisted Instruction Computer-Assisted Instruction (CAI) refers to the use of computers to present drills, practice exercises, and tutorial sequences to the student. One extensive type of CAI system is the PLATO[RALS1993]. It was developed by a group of engineers and educators in the Computer-based Education Laboratory at the University of Illinois, Urbane. Stanford University operated CAI system to distribute instructional computing to a number of centers throughout the United States. 2.2 Intelligent Computer-Aided Instruction Computer-Assisted Instruction (CAI) refers to the use of computers to present drills, practice exercises, and tutorial sequences to the student . One extensive type of CAI system is the PLATO [RALS1993]. It was developed by a group of engineers and educators in the Computer-based Education Laboratory at the University of Illinois, Urbane. 3.0 THEORETICAL FRAMEWORK 3.1 ICAI Computer programs that use artificial intelligence principles to help a person are called Intelligent Computer-Aided Instruction. 3.1.1 Major Characteristics Shown in Figure 1.0 are the four major characteristics that an ICAI program should have. 3.1.2 Mixed-Initiative Dialogue Mixed-Initiative dialogue is on e of the most distinguished aspects of ICAI programs. A more important characteristic of ICAI program from a design perspective is that they are constructed as knowledge networks.

g. Bibliography (References and Citations) This section deals with the nature of reference materials (e.g. Books, Unpublished Materials, Journals and Periodicals, etc.) if one wishes to read further in the area of problem or corollary areas. It also speaks of the researchers awareness of the literature in his field and his critical resources.

Citations, as they appear within the text, should be coded to reflect the first four characters of the principal authors lastname suffixed by the year of publication. Thus, [MILL1991] refers to the publication of Faron Miller for his work published 1991. If Miller has another publication for the same year, the code is appended with an alphabet in lowercase. Thus, a second publication of Miller should be coded as [MILL1991a], while a third should be coded as [MILL1991b]. Book: <code> <authors name>(<year of publication>). Book Title <site of publication>: <complete name of publisher>. Example: [CHIC1986] J M Chiclov (1986). An Introduction to Distributed and Parallel Computing. Hemel Hempstead: Prentice-Hall International (UK). Ltd. <authors name> (<year of publication>). <article title>, Journal Title, volume number (issue number), <pages where article could be found>. Example: [BAET1988] J C M Baeten & J A Bergstra (1988). Global Renaming Operators in Concrete Process Algebra, Information and Computation, 78(3), pp 205 245. <authors name> (<year of publication>). <article title>, In: Conference Name(editors of the proceedings, ed), <pages where article could be found>, <site of publication>: <complete name of publisher>. Example: [PARK1981] D H E Park (1981). Concurrency and Automata on infinite Sequences, In: Fifth GI Conference (P Deussen, ed), pp 167 183, Berlin Springer-Verlag.

Journal: <code>

Conference: <code>

World Wide Web: <code> <subject of the page> (year). Homepage Title. URL site Example: [CRUZ1995] J Cruz (1995). The Home Page of Juan De La Cruz http://dlsu.edu.ph/aguinaldo. Note: Do not use the Traditional Style of Footnoting

2.0

Title Page The first page of a thesis is the title page. The title page presents the title, the full name of the writer, and the submission statement, which includes the faculty or school, and the institution,

the degree sought (granted), and the month and year in which the degree is to be (or was) granted. Thesis Title The title of the project should be concise as well as descriptive and comprehensive. It is a distinctive name given to the project describing the work scope in a specific context and indicates the content of the paper. Generally, project titles begin with a noun or present participle form of an action verb. IT is advisable to state the project titles in general forms in order to bundle a number of problem areas. Humorous or catchy titles are not appropriate and are discouraged. 3.0 Adviser Recommendation Sheet No final thesis documentation will be accepted if the thesis adviser does not duly sign all copies. The Advisers Recommendation Sheet provides space for the signature of the adviser of the group indicating that he/she has examined and recommended the thesis for acceptance and approval. 4.0 Dean and Thesis Coordinators Acceptance Sheet No final thesis documentation will be accepted if the dean and the thesis coordinator do not duly sign all copies. The college acceptance sheet provides space for the signature of the Dean and Thesis Coordinator of the college indicating their acceptance of the work. 5.0 Panels Approval Sheet No final thesis documentation will be accepted if all the defense panelists do not duly sign all copies. The approval sheet provides space for the signatures of the members of the panel indicating their acceptance of the work. 6.0 Table of Contents Observe the following format.

TABLE OF CONTENTS (In bold characters, font size 14) 1.0 Introduction 1-1

1.1 Background of the Study 1.2 Statement of the Problem 1.3 Statement of Objectives 1.3.1 General Objective 1.3.2 Specific Objectives 7.0 List of Appendices. Observe the following format. APPENDICES (in bold character, font size 14) Appendix <appendix #> Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F Appendix G Appendix H Appendix I <Appendix Caption> Project Schedule and Work Assignment Certification Transcript of Interview Survey Forms/Questionnaire Sample Forms and Reports Screen Design Users Manual Program Listing Others

1-1 1-2 1-3 1-3 1-3

Project Schedule and Work Assignment Observe the following format.

Project Schedule
ACTIVITIES Planning 6/19 6/26 7/3 7/10 7/17 12/18 12/25 1/8

<subtask1> <subtask2> System Analysis <subtask1> <subtask2> System Design <subtask1> <subtask2> System Development <subtask1> <subtask2> System Implementation <subtask1> <subtask2> Others

Use a Gantt Chart, a scheduling chart, which marks off time periods in days, weeks or months. This chart must illustrate the different activities performed, when each begins, and when each terminates. The left-hand column are listed the tasks or activities to be performed. The right-hand portion of the chart has horizontal bars that show the duration of each activity. A Gantt chart is based upon time intervals and does not show the logical flow of information throughout a system. It shows the total time involved from the beginning of the project to its completion. Work Assignment Identify the project involvement and participation of each group members. Certifications Include the following certifications: Certificate of Interview Certificate to Use Companys Data / Information Certificate of Acceptance Transcript of Interview* - Contains documentation of all questions and answers obtained during the data-gathering step. Survey Forms/ Questionnaires* Sample Forms and Reports* Screen Design Observe the following format:

Screen No: <screen #> Screen Name: <name of the screen> Narrative Overview: <brief description about the different components of the screen describing its functionality> Example: Screen No: 1 Screen Name: Login Screen Narrative Overview: Allows the user to try to enter the correct user name and password within twenty seconds. Screen Layout: Users Manual A users guide in using the system. The manual is consist of sample screens and their corresponding description, instructions on how to perform specific tasks or use specific object, and a complete illustration of the systems usage (description that will assists the user on how to use the system). Program Listing This contains a printed copy of all the programs, module, functions and procedures of the developed system. 8.0 List of Tables Observe the following format: LIST OF TABLES (in bold characters, font size 14) Table <chapter#>-<table#> <Table Caption> Examples: Table 1-2 Percentage Ration of Sophomore vs. Seniors Table 3-4 Mortality Rate of THESIS2 vs. School Year List of Figures Observe the following format. LIST OF FIGURES (in bold characters, font size 14) Figure <chapter#>-<figure#> <Figure Caption> Examples: Figure 2-2 System Development Life Cycle Figure 4-1 Data Flow Diagram 10.0 Acknowledgement

9.0

The acknowledgement section contains expression of appreciation for assistance and guidance. The given by the advisers and readers does not require written acknowledgement, but the recognition of generosity with time and knowledge is a courtesy that is widely appreciated. Acknowledgements should be expressed simply and tactfully and should fit into a single page only. 11.0 Abstract From 150 to 200 words using direct and complete sentences, the content should be informative enough to serve as a substitute for reading the thesis itself. This should contain a very brief rationale and statement of the problem or issue, a brief description of the research method and design, major findings and their significance, and the conclusion. Do not put any citations or quotations. An abstract is usually limited to one page. Do not start the Abstract with This thesis paper project 12.0 Resource Persons For each resource person: <Full name and Title> <Profession> <Department> <Name of Institution> <e-mail address/ tel. no> 13.0 Personal Vitae For each proponent: <Last Name>, <First Name>, <Middle Initial> <Address 1> <Address 2> <Address 3> <Tel. Nos> <pager and cellular phone nos.> <e-mail address> 14.0 The Text (or Body) The text, or body, of a thesis begins with the first page of Chapter 1. All pages are numbered, including chapter and section title pages. Start using Footers in this part. 1.0 Introduction 1.1 Background of the Study Cruz, Maria Josefa F. 269 San Marcelino St., Golden Gate Subd., Tambo Pasay City 1300 833-8972/ 831-2213 1277-89221/ 0981-8711622 maria@skyinet.net Dr. Juan Dela Cruz Faculty Information Technology Department Systems Technology Institute jdc@sti-edu.net 840-5618/ 8181621 loc. 301

This section gives background information on the study by discussing any or all of the following in textual paragraph form: A. The general area in Computer Science or Information Technology, where the study may be classified. Examples are the following: 1. For Payroll, Accounts Receivable/Payable, Inventory, Reservation, Library, etc. Systems, the general area which may be discussed is Information Systems. 2. For Expert Systems, CAIs, ICAI, ITSs, etc., the general area is Artificial Intelligence. 3. For Editor Softwares, Utility Softwares, Compiler, etc., the general area is Software Technology. 4. For Multimedia Systems, Geographical Information System, Hypertext. etc., these are the actual general areas. B. The current state of technology on the general area leading to the current state technology in the specific area. C. The specific company/corporation/institution on which the study is being conducted. A brief history, organization, some statistics (e.g. number of employees, location/ Branches, etc.) products and/or services, etc. D. A general and brief description of the system under study. 1.2 Statement of the Problem A. Current problems that are evident with the system or area under study. These problems may not necessarily be the problem of the study. B. The problem of the study. Answering the question identifies this: What is being solved by this research or thesis project. The statement of the problem is a clear, definite, and logical statement of the major problem(s) and the sub-problem(s) if any. How to write the problem. State a general problem or issue of the current situation/ system. State the problem fully and precisely in enumerated form. State the problem in complete grammatical sentence, punctuation is important. Provide justification to support the statement. 1.3 Objective of the Study 1.3.1 General Objective This is a statement that what the research or thesis project is trying to accomplish. 1.3.2 Specific Objectives These are statements that try to achieve the general objective. Specify the things that would be done to accomplish the general objective. Objectives are statements of WHAT the project is expected to accomplish. Each objective should be stated to describe what is to be done. Since objectives are associated with action, they usually start with action verbs.

Starting project objectives: The study aims to develop conduct assess design implement enhance produce train strengthen acquire improve evaluate A satisfactory objective should be Specific, Measurable, Attainable/Achievable, Realistic, and Time-bounded. It should be stated to include the following information: a) an action verb; b) the outcome to be accomplished; c) the time-frame the outcome is to be accomplished; and d) the criteria or conditions for measuring the accomplishment Few objectives should be considered in a proposal and they should be arranged in their order of importance. It is more likely that few objectives can be successfully accomplished given the available resources. Objective must always relate to the expected outcomes or project outputs. Moreover, objectives determine the methodology how each objective is to be accomplished. Objectives are normally classified as general and specific. A general objective states what the research or thesis project is trying to accomplish. Specific objectives are statements that try to achieve the general objective. Example: 1. System Development Inventory System General Objective The project aims to improve the current inventory system of XYZ Company by reducing 80% of time needed between the project request and goods delivery before the end of the fiscal year. Specific Objectives Specifically, this study aims to: Improve the procedures for verifying invoices and shipments; Add an inventory control function to hold frequently used parts; Integrate the Goods Received System (GRS) and the Project Ordering System (POS) to reduce the manual effort needed to maintain information flows between these two computer systems. Analysis of the objectives: Criteria Justifications Specific? YES! Because the objectives state particular, precise and definite details about the project.

Measurable? Attainable? Realistic? TimeBounded?

YES! Because the objectives state weighable (80%) indicator to measure the success of the project YES! Because the procedures, function and integration of GRS and POS is feasible and within reach YES! Because the objective states practical and viable methodology YES! Because the objective states the time when the system will be accomplished.

1.4 Significance of the Study A discussion on who benefits from the output of the research or thesis project. Discusses the contributions/benefits of the study to 1. Individuals 2. Corporations 3. Country 4. World or humanity in general The resources allocated for the purpose research (human, financial and material) should be justified in terms of expected utility/significance of the results for the following concerns: 1. Nationhood and Development Will the research produce new technology? Does research address current social economic political and cultural problems? Will innovation natural infra and human rescue management results from the study? 2. Scientific and Artistic Domain Will the research contribute new information? Are data gaps to be filled? Is a new point of view to be applied to a previously studied phenomenon? 3. University Trust Will contribute to expansion of knowledge? Will it develop strong scientific base for national mastery? Will it develop strategies to address present socio-economic? 4. Specific Users/Beneficiaries Will it benefit specific users? How it benefits those users? 1.5 Scope and Limitation Discusses the boundaries of the system to be developed Enumerates items shall will not be covered by the study Gives a general view of the features/characteristics of the output of the system. Assumptions made about certain things stated in this section These are statements of what can be taken for granted about research project

2.0 Methodology of the Study

Identifies the formal method that the proponents intend to follow in order to accomplish what have been see in the objectives. The formal methodologies are any of the software engineering systems analysis and design methodologies. 1. Waterfall model or Software Development Life Cycle (SDLC) Model System Engineering and Analysis Software Requirements Analysis Design Coding Testing Maintenance 2. Prototyping Requirements Gathering and refinement Quick Design Building Prototype Customer Evaluation Prototype Refining Prototype Engineer Product 3. The Spiral Model Planning Risk Analysis Engineering Customer Evaluation 4. 4th Generation Techniques Requirements Gathering Design Strategy Implementation using 4GL Testing 5. Rapid Application Development Requirements Planning User Design Construction Cutover 6.Join Application Development 3.0 Review of Related Studies A. General Literature Survey resource according to your major or area of study B. Abstract/ Compiled Abstracts crude sources of material C. Bibliographical References Bibliographic or bibliographies D. Directories and Periodical grades E. Trade Literature National Journals research and development trend in the country Information Journals research and development at international level

F. Personal Interviews ask the following persons about the field of studies, conclusions, recommendations for future works, present and future trends of particular research, advice, etc. G. Persons in the same professional major H. Persons who have done research at the same professional level I. Adviser/faculty members from yours and other universities J. Go to industry/Research Institutes/Government Agency /Private Corp interview/visit site and inquire the following: Inquire in their past project, recommendation, future works not need to be done, problems encountered, limitation and coverage of works. Inquire about present projects (if possible) See their facilities, library and laboratory Try to interview their staff and personnel K. Evaluation of Existing System Software Literature or Background of the study will: Reveal Investigation Similar to the study how, other researchers approach the problem Suggest method or technique of dealing with problems, suggest approach and strategies Reveal significant research personalities See your study in historical/associative/perspective Provide new ideas and new approaches Assist you in evaluating your own research effort Provide information on what is current in terms or similar technologies and solution to particular problem domain. 4.0 Theoretical Framework The theoretical foundations in computer science those are necessary to accomplish the objectives set need to be discussed thoroughly and sited accordingly. It is structure that holds together/ supports the fundamental principle of the study and requires giving legitimate basis defining the area of research. Examples 1. For Games Software: game trees, search algorithm 2. For Information System: general system theory, transaction processing system, human compiler interface, etc. 3. For CAis,ICAIs, ITSs learning theories, assessment theories, etc. 4. For Expert System search engines, knowledge bases, etc. 5.0 Documentation of the Current System This section should provide necessary information on the current situation/system such as its name, its description, user/beneficiaries, etc. 5.1 Description of Current System 5.2 Hardware Setup 5.3 Software and Application being used 5.4 Personnel 6.0 Data Gathering Procedure and Output

This section produces on gathering data such as interview, survey/questioners, etc. It also includes tryouts and other validation procedures, observation techniques, distribution and collection of questioners and whichever approach (es) is/are to be employed is/are described. All each procedure, an accompanying output should also be described. If needed statistical treatment of data using statistical formulas and procedures are described. 6.0 Requirements Analysis and Specifications The Analysis part is the most important section of the document. In some researches, this is sometimes referred to as Analysis and Interpretation of Data. Some important parts in this section as follows: Detailed discussion of the application of the research methodology of the data gathered Detailed discussion on how the solutions to the problems stated were formulated Detailed discussion on how the objectives of the study were met. Detailed interpretation of the results Basically, all the HOWs of the research should be stated narrative in this section. The Analysis section should answer any questions about the validity of the conclusion. This section is the expansion or development of points rose in the introduction and methodology and consists of facts and figures translated onto supportive, narrative description or explanation. The discussion should be organized and arranged in clear, associated points/paragraphs to support the main research output. Sample organizations of paragraphs are: What did you do? How did you do it? What happened? A specific analysis tool should be used to illustrate existing system and requirements of the projects. Then analysis tools that may be used are: Hierarchal Input-Output (HIPO) Chart Data flow diagrams Entity-Relationship Diagram System Flowchart 7.0 System Design Specification This section should provide models that depict information (data and control ) flow and content, portion the system functionally and behaviorally and depict the essence of what must be built. Deliverables from the Design of System Internals 1. Structure Chart Hierarchical diagram that show how an information system as organized a) Bully factored structure charts b) Complete description of data compiles and flags 2. Module Specifications a) Input Specifications i. Database Specifications ii. Other Input Specifications 1) On-line or Batch 2) Files 3) Other modules

b) Processing Specifications i. Pseudocode ii. Nassi-Shneiderman Charts c) Output Specifications i. Database and file update specifications ii. Print or on-time specification iii. Other modules 8.0 System Requirement Specification 8.1 Hardware Requirements 8.2 Software Requirements 8.3 Human Resource Requirements The requirements definition describes everything about how the system interact with its environment. Includes are the following kinds of items: Physical Environment Where is the equipment to function? Is there one or several locations? Are there any environmental retractions such as temperature, humidity or magnetic interference? Interfaces Is the input coming from one or more other system? Is the output going to one or more other system? Is there a prescribed way in which the data is formulated? Is the prescribed medium that the data must use? Users and Human Factors Who will use the system? Will there several types of user? What is the skill level of each type of user? What kind of training will be required for each type of user? How it easy will it be for user to understand and use the system? How difficult it will be for a user to use the system? Functionality What will the systems do? When will the system do it? How and when can the system be changed or enhance? Are there constraints in execution speed response time or throughput? Documentation How much the documentation is required? To what audience is documentation addressed? Data 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?

Resources

How must data flows through the system? Must any data be retained for any period of time? What materials, personnel, or other resources are required to built, use and maintained the system? What skills must the developers have? How much physical space will be taken up by the system? What are the requirements for power, heating or air-conditioning? Is there prescribed timetable for development? Is there a limit on the amount of money to be spent on development or on hardware and software? Most access to the system or information is controlled? Flows will one users data is isolated from others? How will user programs be isolated from other programs and from the OS? How often will the system be backed up?

Security

9.0 Conclusion and Justification This section should discuss what has been accomplished in the study written in the objective to see clearly all the significant aspects. It may be subdivided into those that are primarily esthetic, those that announce the results on an investigation, and those that present discussion concerning in the course of action. Also, if may be numbered with respects to problems and sub-problems in the study. 10.0 Recommendation This section should finish future undertakings base on the analysis and conclusion of the stud. It may also recommend potential application of the study, other solutions, enhancement and/or development related to the study.

Anda mungkin juga menyukai