9/13/2013
IT SPECIAL PROJECT DOCUMENTATION
Capstone Project
This Project in Information Technology course allows the students to demonstrate a broad knowledge of the topics covered in the BSIT curricula by undertaking an approved project that ranges from a major research paper (mini-thesis) to a technology development project.
9/13/2013
ABSTRACT
BRIEF Summary of the Project- 200 words Contents Overview of the Problem Project Design
SW and HW
Result of the Project
Did the system solve the problem? Did it attain the objectives of the study?
PREFACE
Contents:
Statement of the Problem Significance of the study/Rationale The proposed system Structure of the project document
9/13/2013
THE INTRODUCTION
1.1 Statement of the Problem General problem that the system addresses The need to find a solution Significance of finding the solution to the problem
THE INTRODUCTION
1.1 Current State of the Technology
What is actually happening (e.g. Accounting System) - Discuss the actual situation/specific problems that exist in the company/institution under study Review of Related Literature (Similar Studies)
Discuss the different solutions using similar /related studies Search for existing literature in your area of study; Review the literature selected; how did these studies solve the problems of the system? What are its advantages and advantages?
9/13/2013
THE INTRODUCTION
1.1 Current State of the Technology
What is actually happening (e.g. Accounting System)
Today, accounting information system has integrated into business information systems of a company. As soon as accounting information system provides information necessary for internal and external reports, it becomes a vital component of decision making process. Internet technologies play an important role in the development and implementation of accounting systems as well. Internet facilitates direct transactions between customers, suppliers and businesses It is also important that a present day accounting system has to be adopted not only to fast changes in technologies, but also to accelerate changes in accounting standards (Arnold, Blisard, and Duggan , 2012).
THE INTRODUCTION
1.1 Current State of the Technology
Discuss the actual situation/specific problems that exist in the company/institution under study
Example Amidst the global trends in the use of technology nowadays, ABC Company continues to be confronted with several issues with regard to their use of accounting information system. Inevitable errors continue to occur in the computations and the preparation of financial reports.
9/13/2013
THE INTRODUCTION
1.1 Current State of the Technology -Review Related Studies
Several studies agree that integrating technology in the information systems provides positive results. For instance, the study of Alsharayri (2012) about the impact of the use IT in the accounting system of the Jordanian Telecommunications companies revealed a positive impact for the information technology on the effectiveness of accounting information systems, where the average of the paragraphs' means for the hardware, software, networks and databases reached to (3.4924)
Moreover, International Federation of Accountants(2002) believes that ebusiness plays an important role in accounting systems, through changing business processes and the evidence available to support business transactions, which leads to changes in the accounting records and procedures. IFAC reveals that automatic transmission of information and data on operating activities directly into the accounting system through the use of integrated software solutions may become efficient.
CHAPTER 1 LAYOUT
Chapter 1 INTRODUCTION
1.1 Statement of the Problem 1.2 Current State of Technology 1.3 Objectives 1.3.1 General Objective This study aimed to design a Computerized Accounting Information System for the ABC Company
9/13/2013
CHAPTER 1 LAYOUT
Chapter 1 INTRODUCTION
1.3.2 Specific Objectives
This study intended to do the following:
1. To design a user friendly interface for the system 2. To provide a search engine for easy retrieval of data.
....
n. To generate the following reports a. List of payments
NOTE: The objectives must be based from the problem statement
1.4 Definition of Terms
CHAPTER 1 LAYOUT
Chapter 1 INTRODUCTION
1.4 Definition of Terms
Devices are different types of computers and basic equipment thereto, which are used for data reception, processing, storing and retrieving it to be used in decision-making. Software is a set of systems that operate devices, networks and databases which make devices capable of carrying out the required operations that are commensurate with the activities of the organization.
9/13/2013
Chapter 2: Theoretical Framework A Theory is a statement that is much broader than facts; the basis of policies and practices in a particular discipline that gives direction to the researcher s solution of the research problem. (Polit and Hungler, 1991). A descriptive theory consists of a set of related statements describing or explaining a phenomena systematically. It explains why an event is associated with another event or what causes an event to happen. A Framework - is a real or conceptual structure intended to serve as a support or guide for the building of something that expands the structure into something useful.
THEORETICAL FRAMEWORK
focuses on a broad , general explanation of the relationships between concepts of interest in a research study. It is founded in one existing theory or a combination of two or more theories
9/13/2013
THEORETICAL FRAMEWORK
Sample Contents of a Theoretical Framework of CAIS Data and Information Information Systems Accounting Information Systems
Accounting as Information
Functions of Accounting Information Systems Characteristics of Accounting Information Systems
THEORETICAL FRAMEWORK
EXAMPLE 2: POS System with Mobile Inquiry and IVRS.
Discuss the following theories in details
2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.2.6 IVPRS TRANSACTION PROCESSING SYSTEMS NETWORK TECHNOLOGY POINT OF SALE AUTOMATED TELLER MACHINE WAP/SMS TECHNOLOGY
9/13/2013
CHAPTER 2 LAYOUT
Chapter 2 THEORETICAL FRAMEWORK
2.1 Introduction
This chapter presents the different theories that support the development of this project
2.2 Theoretical Framework 2.2.1 Client-Server Computing 2.2.2 Theory of Web Design 2.4 Summary
CHAPTER 3: THE SYSTEM
3.1 Introduction Explains how the system solves the problem stated in the Statement of the problem. . This chapter presents the. 3.2 System Design Specification Overview of the Design Specification and functional requirements of the system
System design
A. B. C. D. E. EXTERNAL SCHEMA CONCEPTUAL SCHEMA LOGICAL SCHEMA PHYSICAL SCHEMA IMPLEMENTATION
9/13/2013
CHAPTER 3: THE SYSTEM
CHAPTER 3: THE SYSTEM
10
9/13/2013
CHAPTER 3: THE SYSTEM
REQUIREMENTS DETERMINATION
CHAPTER 3: THE SYSTEM
A. EXTERNAL SCHEMA Organizational Scenario Problems with the existing system Functionality of the organization Information Systems Architecture Enterprise Data Model
11
9/13/2013
CHAPTER 3: THE SYSTEM
3.1 Introduction Introduce how the system will solve the problem cited in the problem statement 3.2 System Design Specification
Discuss the method used in the design Discuss the processes in the design of the system Requirements Determination (using SDLC, Prototyping etc) This study used the SDLC model in developing the system. Discuss in detail how you gathered the data
Organizational Scenario Problems with the existing system Functionality of the organization Information Systems Architecture Enterprise Data Model
EXTERNAL SCHEMA
CHAPTER 3: THE SYSTEM
EXTERNAL SCHEMA (ACCOUNTING SYSTEM)
Sample entities that can be derived out of the Data gathering procedure. STUDENT STUDENT FEES RECORD OTHER INCOME RECORD DAILY FEES COLLECTION STAFF CHEQUE ISSUING REGISTER LEDGER SALARY & INCOME TAX STATEMENT
12
9/13/2013
CHAPTER 3: THE SYSTEM
EXTERNAL SCHEMA (ACCOUNTING SYSTEM)
Sample entities that can be derived out of the SDLC process
Fees Receipt
Receipt Generation Daily Fees Collection Book Individual Student Financial Record Foreign Currency Register
Expenses
Cheque Issuing/Payment Register Head of Expenditure
Cash Book Maintenance Salary and Income Tax Slips for IIPS faculty and staff Student Record Maintenance Staff Record Maintenance Login and Registration Services
CHAPTER 3: THE SYSTEM
3.2.1 ENTERPRISE DATA MODEL This EDM identifies how the organization works and how the tasks or the entities are dependent on each other. Here we can notice a broad distinction between the income section and the Expenditure section with the Cash Book providing a connection between them.
13
9/13/2013
CHAPTER 3: THE SYSTEM
WHAT IS EDM?
An EDM is a data architectural framework used for integration. It enables the identification of shareable and/or redundant data across functional and organizational boundaries. As a data architectural framework, an EDM is the "starting point" for all data system designs. The model can be thought of much like an architectural blueprint is to a building; providing a means of visualization, as well as a framework supporting planning, building and implementation of data systems.
CHAPTER 3: THE SYSTEM
3.2.2 DATA FLOW DIAGRAMS DATA FLOW DIAGRAMS CONTEXT DIAGRAM(level 0) LEVEL 1 LEVEL 2
. ..
LEVEL n
14
9/13/2013
CHAPTER 3: THE SYSTEM
D. CONCEPTUAL SCHEMA
Entities Relationship among Entities Relationship Definitions Structural Constraints Operational Constraints
CHAPTER 3: THE SYSTEM
CONCEPTUAL SCHEMA
STUDENT
STUDENT FEES RECORD OTHER INCOME RECORD DAILY FEES COLLECTION
STAFF
CHEQUE ISSUING REGISTER LEDGER SALARY & INCOME TAX STATEMENT
15
9/13/2013
CHAPTER 3: THE SYSTEM
CONCEPTUAL SCHEMA
Discuss Entities used in detail
CHAPTER 3: THE SYSTEM
3.2.3 ENTITIES COURSES information about the various courses and their roll
information
FCREGISTER to keep track of Foreign Currency SEMFEES to note the fees of each batchs semester, category wise OTHERRECEIPTS to keep track of Cash incomes HEADS OF EXPENDITURE which heads of expenditure are
allowed
16
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.4 DEFINITION OF RELATIONSHIPS
CHAPTER 3: THE SYSTEM
DEFINITION OF RELATIONSHIPS
17
9/13/2013
CHAPTER 3: THE SYSTEM
CONCEPTUAL SCHEMA
Definitions of Attributes Domain Constraints Operational Constraints
CHAPTER 3: THE SYSTEM
3.2.5 DATA DICTIONARY
TABLENAME
Description Alias Attribute Name BID
BORROWER A record for each person who is able to borrow books from library
None Description
ID number of student or staff member Student or staff member last name Student or staff member first name Student or staff member Middlename Borrower Email Borrower Category
Data Type Text
Default Value None
Example 098-2010-01
Nulls Allowed (Y/N) N
length 11
Validation Rule 098-XXXX-XXX
BLastName
Text
None
Dela Cruz
30
BFirstName
Text
None
Juan
30
BMname
Text
None
Dela Pea
30
Bemail Bcatagory
text text
None Student
x@yahoo.com Student
N N
20 15
In format a.b@c Student, staff, honorary
NOTE: INCLUDE ALL ATTRIBUTES IN THE RELATION
18
9/13/2013
CHAPTER 3: THE SYSTEM
OPERATIONAL CONSTRAINTS
The Operational Constraints :- The operational Constraints identify the constraints that affect the business. Let us take the business rule -An entry can be made in the cash book only for an entry in the Daily Fees Collection or in the Expenditure. Here the Constrained Object is the CASH BOOK (Entity) And the Constraining Object is the DFC and EXPENDITURE (Entities)
CHAPTER 3: THE SYSTEM
3.2.6 OPERATIONAL CONSTRAINTS
Business Rule 1: An entry can be made in the cash book only for an entry in the Daily Fees Collection or in the Expenditure.
Constrained Object: CASH BOOK (Entity) Constraining Object: DFC and EXPENDITURE (Entities)
Business Rule 2: Monthly Salary and Income Tax slip is not generated for Visiting Staff.
Constrained Object: Post (Attribute of Staff) Constraining Object: MONTHLY SALARY SLIP and INCOME TAX SLIP (Entities).
Business Rule 3: Expenditure can only be for a stated Expenditure Head.
Constrained Object: EXPENDITURE (Entity) Constraining Object: EXPENDITURE HEAD (Entity).
The Operational Constraints :- The operational Constraints identify the constraints that affect the business.
19
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.7 ENTITY RELATIONSHIP DIAGRAM/UML CLASS DIAGRAM
CHAPTER 3: THE SYSTEM
ENHANCED ENTITY RELATIONSHIP DIAGRAM
3. LOGICAL SCHEMA
Input Output Screens Transactions that will be run on the system Entity Identification and description Relational Schema
20
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.8 INPUT/TRANSACTIONS/OUTPUT SCREENS Fees Receipt
Input Screen will provide an interface to the user to enter the details of the fees. Transactions The system should perform the necessary checks from the various relations about the data , make entries into the tables concerned ( SFR, DFC, and Cash Book). Fees Receipt Output will be in the form of a printed receipt which will show the details and amount of fees paid.
Salary Slip and Income Tax Slip Generation
Input Screen to enter the details of the salary and income tax of various staff members Transactions enter the details in the database (MSS,ITS) Output will be in the form of a printed salary and income tax slip
INPUT/OUTPUT SCREENS are TRANSACTIONS that will be run on the system
CHAPTER 3: THE SYSTEM
Expenditure
Input Screen to enter the details of expenditure like the name of firm , particulars , Cheque number, etc. Transactions entry into required fields in the database. Output No such printed output is generated for every transaction. Output may be seen in the form of reports.
Record Entry Record Entry is to provide an interface to enter the details of persons connected with the system in any way. Such persons are Students, Staff Members and authorized users of the system. Once the details of a Student or Staff have been entered, it requires no further entering in the system.
21
9/13/2013
CHAPTER 3: THE SYSTEM
Transforming ER into relations Functional Dependencies Normalization
In the relational model, we first convert the ER diagram into relations, following which we identify the functional dependencies between the attributes of relation and then normalize the relations so that there are no dependencies.
CHAPTER 3: THE SYSTEM
Receipt Number Se m Roll Bank Branch Old Receipt Number Tuition Fees Cautio n Money Library Fees Hoste l Fees Sports Fees Placement Fees Universit y Fees Examination Fees Misc Fees USD Fees Due/Exces s Total Fees Paid Pound Fees
STUDENT FEES RECORD
DD Date
DD Number
22
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.9 RELATIONAL SCHEMA STUDENT RELATION
CHAPTER 3: THE SYSTEM
FUNCTIONAL DEPENDENCY
Let us consider the entity DD LIST . This entity has the attributes : DD DATE , DD Number , Bank and Branch , Amount and Print Date . We can see that this entity has no partial dependency as all the attributes are fully functionally dependent on the primary key.
23
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.10 FUNCTIONAL DEPENDENCIES
CHAPTER 3: THE SYSTEM
3.2.10 FUNCTIONAL DEPENDENCIES
We break STUDENT relation into STUDENT and ROLL ENROLL relations through Normalization
24
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.10 FUNCTIONAL DEPENDENCIES
Indicate all Functional dependencies of each relation/table
In the normalization process , we break relations that have partial dependencies. The process of normalization completeS the phase of the Logical Schema.
CHAPTER 3: THE SYSTEM
PHYSICAL DESIGN
Designing Physical Records Final Relations Indexes
25
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.11 FINAL RELATIONS/TABLES
CHAPTER 3: THE SYSTEM
3.2.13 INDEXES Indexes are required for faster access of data. Considering the entity Daily Fees Collection, we can have an index on the DAtE_DFC of the Receipt Number.
26
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.12 INDEXES EXAMPLES: Entity : Daily Fees Collection Index : Date_DFC or ReceiptNumber Justification : It can be inferred that the transactions with this relation will take place in the serial order of the above attributes. Entity : Student Index : Roll Number Justification :The records of students are entered as per their roll numbers. The system will normally use the latest entry of the roll numbers.
CHAPTER 3: THE SYSTEM
5. IMPLEMENTATION
Snapshots of the working system Hardware and Software requirements
27
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.13 THE WORKING SYSTEM 3.2.14. 1 The splash screen and the login screen. Only those users who have proper authorization by a user name and a password can use this system.
The splash screen
CHAPTER 3: THE SYSTEM
3.2.13. 2 The menu options after a successful login
28
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.13.3 Fees receipt is the screen that is used to print a receipt to a student who has paid the fees. The receipt of fees is in the form of a demand draft only. After entering the roll number, the information about the student appears on the right hand side. The other details are filled by the operator.
CHAPTER 3: THE SYSTEM
3.2.13.5 REPORT GENERATION A. Fess Collection Report
29
9/13/2013
CHAPTER 3: THE SYSTEM
3.2.13.5 REPORT GENERATION B. Fess Payment Report
CHAPTER 3: THE SYSTEM
3.2.14 Hardware and Software Requirements The implementation of this system had the following requirements : Intel Pentium 3 1 GHz 128 MB RAM 20 GB Hard Disk Drive other standard Components Microsoft Windows 2000 Professional Oracle 8i Enterprise Edition Microsoft Visual Basic 6.0 Enterprise Edition Microsoft Word 2000 Microsoft PowerPoint 2000
30
9/13/2013
CHAPTER 3: THE SYSTEM
3.3 Summary
CHAPTER 3: LAYOUT
Chapter 3 The System 3.1 Introduction 3.2 System Design Specification
Discussion about the method used in system design Discussion about the process used in the system design
3.2.1 Enterprise Data Model 3.2.2 Data Flow Diagrams 3.2.3 Entities 3.2.4 Definition of Relationships 3.2.5 Data Dictionary
31
9/13/2013
CHAPTER 3: LAYOUT
Chapter 3 The System 3.2 System Design Specification(cont d) 3.2.6 Operational Constraints 3.2.7 Input/Transaction/Output Screens 3.2.8 Relational Schema 3.2.9 Functional Dependencies 3.2.10 Final Relations 3.2.11 Indexes
CHAPTER 3: LAYOUT
Chapter 3 The System 3.2 System Design Specification(cont d) 3.2.12 The Working System 3.2. 13 The Hardware and Software Requirements 3.3 Summary
32
9/13/2013
CHAPTER 4: PERFORMANCE ANALYSIS
4.1 Introduction
q q q Major Objectives of the experiments conducted Describe all parameters measured
q Measurable factor
Discuss all assumptions
4.2 Experimental
q List of Experiments conducted in analyzing the performance of the system
q Discussion of the results and observations done on the system q Show proof that the Objectives have been achieved q NOTE: Discuss your results and observations per objective
CHAPTER 4: PERFORMANCE ANALYSIS
4.3 Results and Analysis
q Overview of the Results of the Experiments
q Include sample raw data to explain how these are presented and analyzed q Full set of data shall be included in the appendix
4.4 Summary
33
9/13/2013
CHAPTER 5: CONCLUSION
Discuss the summary in the following order:
the problem The proposed system The major results of performance analysis Recommendations for further work
CHAPTER 5: CONCLUSION
BIBLIOGRAPHY: Writing References using APA: Abu-Musa, A. (2003). The perceived threats to the security of computerized accounting information systems. Journal of American Academy of Business, Cambridge, 3 (1), 9. Retrieved from http://search.proquest.com/docview/222858391?accountid=33511
in-text citation: (Musa, 2003) --- (used at the end of a sentence/paragraph)
OR (e.g.) The study of Musa (2003) revealed that..(used in the beginning of a paragraph/sentence )
34
9/13/2013
ACKNOWLEDGMENT
APPENDICES
Contents of Appendices: APPENDIX A : RAW DATA APPENDIX B : PROGRAM LISTING(Source Code)
Unformatted Fixed width font(courier) List of parts/ components used (e.g. no of PC s; networks) Schematic diagram / physical layout of the Network (indicate the Server and Clients)
APPENDIX C : TECHNICAL MANUAL (HARDWARE SYSTEM)
35
9/13/2013
APPENDICES
Contents of Appendices: APPENDIX D : TECHNICAL MANUAL (SOFTWARE SYSTEM)
Description of the Main program structure Describe each module in your source code
What does this module /procedure/function do? What parameters are passed? How are the parameters used? Which routines call them? And which routines they call? Source code should be printed per module/procedure/or function
APPENDIX E : USERS MANUAL
Should contain detailed procedures on how to set-up and use the system. Use screen shots
APPENDIX F: CURRICULUM VITAE
PHYSICAL FORMAT
8 X 11 Bond paper with 1 margin on TOP , RIGHT, BOTTOM and 1.5 margin on the left side Times New Roman 12 pt Double spaced Pagination- bottom right except at the start of each chapter which shall contain NO page number All pages from cover page to the preface shall use lowercase Roman Numerals while Arabic Numerals shall be used from Chapter 1 Each chapter should start n a new page Each chapter should contain an INTRODUCTION and SUMMARY section
36
9/13/2013
DELIVERABLES
Project Documents q An electronic copy (in CD format) of the project shall be submitted to STI Headquarters containing the following: Project paper documents the review, study design, development, and analysis of the project (refer to ATTACHMENT E to I for the format and outline of the project document), Curriculum vitae of the students, Source Code or Program Listing (e.g., PRG files, VBP files, other modules, etc.), The expected output (i.e., installable if not directly executable) in executable format, Other supporting files (e.g., database/ picture/ video/ audio files, certification, etc.), Readme file contains pertinent information like user names and passwords, installation guide, software and hardware requirements, etc., and AutoRun* an executable program which links the different deliverables.
DELIVERABLES
Project Documents for the STI Koronadal/Tacurong File copy q hardbound (COLOR : BLUE) q An electronic copy (in CD format) of the project shall be submitted to the school containing the following: Project paper documents the review, study design, development, and analysis of the project (refer to ATTACHMENT E to I for the format and outline of the project document), Curriculum vitae of the students, Source Code or Program Listing (e.g., PRG files, VBP files, other modules, etc.), The expected output (i.e., installable if not directly executable) in executable format, Other supporting files (e.g., database/ picture/ video/ audio files, certification, etc.), Readme file contains pertinent information like user names and passwords, installation guide, software and hardware requirements, etc., and AutoRun* an executable program which links the different deliverables.
37
9/13/2013
IMPORTANT NOTICE
Documents will be checked following the arrangement/order discussed in this session. INCOMPLETE DOCUMENTS/PROGRAM: NO FINAL DEFENSE
38
