quatro chapter 6

6.0 Design

6.1 Data Strategies

Before the group considered to place anything up on the system, gathering new information and designing the front endof the site based from the group's perspective is not enough. Users tend to glance at the first simple thing that is useful, examine boastful texts, don't ,make optimal choices and anything unique that captures their sight. One of the principles the group implemented is storage management. Designs under the twitter boostrap provide API's such as the Accordion to offer a simple and responsive way to keep making the system look clean and optimized. The problem towards user's

satisfaction must be taken into consideration since an ugly and vague web design can cause a lot of money. Alignment as an effective design principle helps the group to craft a more compelling User Interface Navigation bars must be proportional to every modules and features of the system to accept user's patience since the less intuitive the design the higher chances of users looking for alternative systems. The most significant strategy that our group in designing our system the strive for simplicity since users put more emphasis in the feature than the design.

6.2 Data Specifications

6.2.1 Entity-Relationship Diagram

The group assessed and analyze the company's entity relationship diagram and here is the list the evaluation of the system's database. The following tables can be seen on our

database. (Please refer to Appendix)

FNB Electronic Document Management System 6-1

The system consists of the following users Author, Vice President Production, Printing Department, Editors, Typesetters, Coordinators and Senior Production Staff.

ProjectMembers. The project members is the focal point of the database since all of the users data are retrieved underthis table. It revolves around all of the system's processessince the information inside is crucial for the progression of the book production. The table's primary key is TeamMemberId, the other key are Position, Fname, Lname, Birthday, Spouse, Address, CellNo, GenderRef_Gender, email, and Password, and PositionRef_position.

Degrees_Earned_ProjectMembers. The table consists of two primary keys; DegreesEarned_DegreesEarned and ProjectMembers_TeamMember. Lists the degrees earned of users.

DegreesEarned. The table consists only of one primary key; DegreesEarned. Lists the degrees earned of users.

ProjectMembers_has_Calendar. The table consists of two primary keys; ProjectMembers_TeamMembersID and Calendar_id. Take notes of all activities of the company's employee.

Project_has_GanttChart. The table consists of two primaray keys; Project_ProjectID and GanttChart_GanttID. Shows that every project requires a Gantt Chart.

Calendar. The table consists of one primary keys; id, other key; tile, d_start, d_end, note, timestamp and by_ip. Responsible for the Notes taken for a single date and Remember Date.

EmployeeReportAudit. The table consists of one primary key; EmployeeReport_ReportNo,; ApproveBy_TeamMemberID and ProjectMembers_TeamMemberID, other keys are DateSigned, and DateApproved. Lists all required information for the auditedDate Signed and Approved of the reports.


EmployeeReport. The table consists of one primary key; ReportNo,; other keys ProjectMembers_TeamMemberID, DateIssued and ReportStatement. Responsible for the Report Number, list of team members that are under the project members and the final report by employees.

EmployeeReportDetails. The table consists of one primary key; EmployeeReport_ReportNo,; other keys Project_ProjectID, Notes and UnitsChapterDone. Lists detailsand information for every Employee.

PositionRef. The table consists of one primary key; position,; the other key description. Lists all descriptionsof positions of project members as references.

Project_Member_role. The table consists of three primary keys; Position_sa_project, ,ProjectID and TeamMemberID. Lists the roles of the project members.

GanttChart. The table consists of five primary keys; GanttID, other keys; StartDate, TaskName and dealine. Listsand displays the status of the task for the project management feature.

GanttChart_has_ProjectMembers. The table consists of two primary keys; GanttChart_Gantt and ProjectMembers_TeamMembers. Lists all of members who are assigned a project since it is required to be tracked for each development.

Subject_has_ProjectMembers. The table consists of two primary keys; Subject_SubjCode, and ProjectMembers_TeamMemberID. Shows the list of Project Members and connect it to their designated subject fields.

Subject. The table consists of one primary key; Subjcode, the other key Desc. The table consists of the Subject identifier for the book and requires descriptions.

Book. The table consists of one primary key; BookID, four foreign keys; Subject_SubjCode, GradeYearLevel_Ref_Lcode,


BookManual_BookManualID and Project_ProjectID, the other keys are Title, PubDate, and Edition. The Book table is the core of the system's data since this is the end product of the organization. It contains information about the Book such as Grade/Year Level, Book Manuals and etc.

GradeYearLevel_Ref. The table consists of one primary key;Lcode, other key is Desc. The table consists of all descriptions for the sub table of the Grade/Year level for the book information.

BookManual. The table consists of one primary key; BookManualID, other key is Title. The Book Manual stores allof the information regarding the book.

Book_has_ProjectMembers. The table consists of two primary keys; Book_BookID and ProjectMembers_TeamMembers. Shows the list of Project Members that are concerned with their designated books.

Project. The table consists of one primary key; Project, other key; DateStarted, Deadline and Description. The information about the progress of the book that was retrievefrom the details done by the company's employee.

Project_Member_Date. The table consists of three primary keys; ProjectID, DateJoined, TeamMemberID, and DateLeft. Connects all of the date that are connected from Project Members, roles and the project itself.

PStatus. The table consists of two primary keys; ProjectID and PStatus. Shows the progress of the project.

PStatusRef. The table consists of one primary key; PStatus, other key desc. Connects the information that references forthe Project Status and book.

Versioning. The table consists of three primary keys; VersionNo ,Project_ProjectID, and File_FileID. other key; ChangeLogs. The table helps tracks the new releases and processes of the project. It also restores some of its


properties and act as a backup data plan when tragedy such as loss of data occurs.

File. The table consists of one primary key; FileID, one foreign key; FileForm_at_FileFormat, other keys; FileName, FileDisc, filesize, dateUploaded, timeUploaded, and fileLONGBOB. Lists all information on the files such as images and manuscripts that are going to be used in the production of the book.

File_has_Category. The table consists of two primary keys; File_ID and Category_Category.

Category. The table consists of one primary key; Category. Segregates all of the files in a Category.

FileFormat. The table consists of one primary key; FileForm,other key; desc. Provides a standard format for all files that are going to be uploaded inside the system.

Comment. The table consists of two primary keys; Notes and File_FileID. Stores valuable information or comments that users can use for future use.

6.2.2 Tables/Files Layout

ProjectMembers.

Field Name Description

Type(Length)

DefaultValue

AcceptedValues

TeamMemberID Unique IDof theTeamMembers

INT 1 AutoIncremental

Fname DesignatedFirst Nameof theuser

varChar(45)

First Name varChar

Lname Designated varChar( Last Name varChar


Last Nameof theuser

45)

Birthday Birthdateof theuser

DATE MM/DD/YYYY DATE

Spouse DesignatedSpouse ofthe user

varChar(45)

Spouse Name varChar

Address DesignatedAddress ofthe user

varChar(45)

Home Address varChar

CellNo DesignatedCell phoneNumber ofthe user

INT Cell phoneNumber

INT

GenderRef_Gender

Gender ofthe user

varChar(1)

M/F varChar

Email DesignatedEmailAddress ofthe user

String [email protected]

String

Password Desiredpasswordof theuser.

varChar(45)

Password varChar

PositionRef_position

Lists thereferencesof thepositionof theprojectmembers

varChar(45)

AUT varChar

Degrees_Earned_ProjectMembers.

Field Name Descriptio Type(Len Default Accepted


n gth) Value ValuesDegreesEarned_DegreeEarned

Unique IDof theUser'sdegree

varChar(45)

DegreesEarned

varChar

ProjectMembers_TeamMemberID

Unique IDof theProjectMembers

INT(11) 1 INT

DegreesEarned.


Type(Length)

DefaultValue

AcceptedValues

DegreesEarned Unique IDof DegreesEarned

varChar(45)

BS-INSYS varchar

ProjectMembers_has_Calendar


Type(Length)

DefaultValue

AcceptedValues

ProjectMembers_TeamMembersID

The listsof all theProjectMemberswho have aspecialization on aspecificsubjectfield

INT 1 None,Incremental

Calendar_id Uniqueidentifierof user'sCalendarfeature



Calendar.


Type(Length)

DefaultValue

AcceptedValues

Id_INT Uniqueidentifiereverytasks madein theCalendarfeature.

INT Note AutoIncremental

Title The namethat willbe givento thetask oreventunder theCalendarfeature.

varChar(45)

Title varChar

D_start Thestartingdate ofthe event.Shows thedaterestriction of theevent.

DATE yyyy-DD-mm DATE

D_end The enddate ofthe event.Shows thedaterestriction of the



event.Note Enables

the userto addadditionalinformation on theirreports

varChar(45)

Notes varChar

Timestamp The datathat holdsthe startdate andtime ofwork.

DATETIME

yyyy-DD-mmHH:mm:ss

DATETIME

By_ip Can beaccessedusingdifferentIP.

varChar(45)

192.168.1.104

varchar

EmployeeReport

Field Name Description Type(Length)

DefaultValue

AcceptedValues

ReportNo Unique IDof theEmployee'sReport


DateIssued DesignatedDate ofIssued


ReportStatement

Valuableinformationregardingatpresent'sReport

varChar(45)

ReportStatement

varChar


ProjectMembers_TeamMembers

Users thatare underthe projectwith theconsent ofthe author

INT 1 NonIncremental

EmployeeReportAudit


DefaultValue

AcceptedValues

EmployeeReportNo

Unique IDof theEmployee'sReportNumber


DateSigned DesignatedDate ofSignage

DATE yyyy-MM-dd DATE

DateApproved DesignatedDate ofApproval


ProjectMembers_TeamMembers

Users thatare underthe projectwith theconsent ofthe author


EmployeeReportDetails


DefaultValue

AcceptedValues

EmployeeReport_ReportNo

Unique IDof eachEmploye's



ReportNotes Enables the

user to addadditionalinformationon theirreports

varChar(600)

Note varChar

UnitsChapterDone

The numberof finishedchapters ofthe book

INT 1 INT

Project_ProjectID

Foreign keythatconnectsall of theprojects'sID to eachEmployee'sreport


PositionRef


DefaultValue

AcceptedValues

Position Unique IDof eachProjectMembersthat has arole andonly storesemployee'spositions.

varChar(45)

AUT varChar(45)

description Enables theuser to addadditionalinformation

varChar(200)

Descrption varChar


on thepositionthey areassignedto.

Project_Member_role.


Type(Length)

DefaultValue

AcceptedValues

Position_sa_project

Thepositionof everymember ontheirdesignatedproject.

varChar(45)

AUT varChar

ProjectID Uniqueidentifier tospecify aProject

INT 1 INT

TeamMemberID Thenumber offinishedchaptersof thebook


GanttChart


DefaultValue

AcceptedValues


TaskName The taskthat isdesignatedfor a user.

varChar(300)

Task Name varChar

deadline The deadlineof theproject thatisdesignatedfor a user.


StartDate The numberof finishedchapters ofthe book


GanttID Uniqueidentifierthat everyprojectrequires aGanttChart

INT 1 AutoIncrement

GanttChart_has_ProjectMembers.


DefaultValue

AcceptedValues

GanttChart_GantID

The lists ofall theProjectMembers whohas adesignatedsubject towork with.



The lists ofall theProjectMembers who



have aspecialization on aspecificsubjectfield

Subject_has_ProjectMembers


DefaultValue

AcceptedValues

Subject_SubjCode

The lists ofall theProjectMembers whohas adesignatedsubject towork with.

varChar(3)

SCI varChar


The lists ofall theProjectMembers whohave aspecialization on aspecificsubjectfield


Subject


DefaultValue

AcceptedValues

SubjCode Lists all ofthe subjectsin a

varChar(3)

SCI varChar


organizemanner.

Desc Enables theuser to addadditionalinformationon thesubject.

varChar(300)

Description varChar

Book.


DefaultValue

AcceptedValues

BookID The mainproduct ofthe system.Containsinformationsuch astitle,author,publisher,location,call numberand subject.


Title The namethat will begiven to theBook.

varChar(75)

Title varChar

Subject_SubjCode

The numberof finishedchapters ofthe book

varChar(3)

SCI varChar

GradeYearLevel_Ref_Lcode

The book'sdesignatedacademiclevel.

varChar(3)

GR1 varChar


BookManual_BookManualID

Uniqueidentifierto specifythe Book'sManual


PubDate The Book'spublishingdate


Edition Theparticularversion of afinalizedtext.

INT 1 INT

Project_ProjectID

Uniqueidentifierto specify aProject


GradeYearLevel_Ref


DefaultValue

AcceptedValues

Lcode Theacamdemiccode givento book'slevel.

varChar(3)

GR1 varChar


varChar(75)

Title varChar

BookManual


DefaultValue

AcceptedValues


BookManualID Uniqueidentifierthatsegregateseach manualof the book.



varChar(75)

Title varchar

Book_has_ProjectMembers.


DefaultValue

AcceptedValues

Book_BookID Uniqueidentifierthatsegregatesthe books.


ProjectMembers_TeamMembersID

The namethat will begiven to theBook.


Project.


DefaultValue

AcceptedValues

ProjectID Uniqueidentifierto specify aProject


DateStarted DesignatedDate of theproject's



establishment

Deadline DesignatedDate of theproject'sdelivery


Description Enables theuser to addadditionalinformationon theproject

varChar(300)

Description varChar

Project_Member_Date.


DefaultValue

AcceptedValues



DateJoined DesignatedDate of theProjectMember'srecruitment


TeamMemberID Uniqueidentifierto specifythe users


DateLeft DesignatedDate of theProject'sremainingtime ofdelivery



Project_has_GanttChart.


DefaultValue

AcceptedValues

Project_ProjectID

Uniqueidentifierthatsegregateseach manualof the book.


GanttChart_GanttID

The namethat will begiven to theBook.


PStatus


DefaultValue

AcceptedValues



PStatus The statusof theproject'sdevelopment

varChar(1)

5 varChar

PStatusRef.


Default Value Accepted

ValuesPStatus The

project'sstatus

varChar(1)

5 varChar


desc Enables theuser to addadditionalinformationon theproject

varChar(200)

Project'sStatus

varChar

Versioning.



ValuesVersionNo The

project'smainversioningcontrol forthe book'sprogress.


Project_ProjectID

Foreign keythatconnects allof theprojects'sID to eachEmployee'sreport


VersionAsOfDate

Thedesignateddate foreachproject'sversions.


ChangeLogs Enables theuser toinput"entries" or

varChar(200)

changelogs varChar


logs to takenote ofeveryprogressfrom the oldversion tothe new one.

File



ValuesFileID Unique ID of

the FileINT 1 Auto

Incremetal

FileName DesignatedFirst Nameof the user

varChar(45)

LightHouse.jpg

varChar

FileDesc Enables theuser to addadditionalinformationon the fileblob.

varChar(300)

FileDescription

varChar

Filesize The size ofthedocument.

LONG 123456789 LONG

dateUploaded Designateddate eachtime aproject isuploaded.


timeUploaded Designatedtime ofstoring the

TIME HH:MM:SS TIME


fileFileLONGBLOB

Theinformationregardingthe size ofthe file'slimitations

INT 123456789 INT

FileFormat_at_FileFormat

Referencetable of thefile formatsupported bythe system

varChar(5)

.jpg varChar

File_has_Category.



ValuesFile_FileID Reference

table of thefile formatsupported bythe File ID

INT 1 INT

Category_Category

Referencetable of thefile formatsupported bythe Category

varChar(45)

People varChar

Category



ValuesCategory Lists all of

the Files itvarChar(45)

People varChar


by the typeof user thatwill handlethe file.

FileFormat



ValuesFileFormat Enables

users tostorevaluableinformationor commentsthat userscan use forfuture use.

varChar(300)

.jpg varChar

Desc Enables theuser to addadditionalinformationon thefile's sizelimitation.

varChar(45)

Desc varChar

Comment



ValuesNotes Enables

users tostorevaluable

varChar(300)

Notes varchar


informationor commentsthat userscan use forfuture use.

File_FileID INT 1 NonIncremental

6.2.3 Data Coding Standards

The proposed system is formed through the use of the Netbeans 7.1.2 platform. In the process of writing the wholecode for the system, the group followed a standard procedurein coding the program from scratch and testing the system.The group’s data coding standards are as follows:

• Track down each of the group's progress with the use of.

• Revisions from the Entity Relationship Diagrams and theUser Interface should be done simultaneously.

• Lists all of the required models and direct access objects for all entities inside the project. Apply the Model-View-Controller concept.

• Lists all of the tables that required functions (add, view edit, delete) to help ease the problem of identifying those tables who are in need of Direct Access Objects.

• Separate all of the CSS, JQuery and other designs are placed in another set of tabs and called if needed. This solves the problem of over coding.

•

Codes Format used in the system• All dates have the format of YYYY/DD/MM


The group decided to use template a simple but elegant. Usersrely on looks and a project that hosts easy navigationprobably will succeed in its future use. The group put a lotof emphasis on the navigation in its features and modules.All buttons that are highlighted have a sub module under it.All eight features are placed in a dashboard horizontally atthe top for easy navigation and sub features on the leftside.

6.3 Screen Specification

Screen Name: 1.0 Home Page ScreenFile Name: Home_Page_Screen.pngDescription: It contains the actual report for each Employeeunder the Production Department.Lay-out:

Screen Name: 2.0 Files Page ScreenFile Name: File_Page_Screens.png


Description: It contains all of the files needed for theproject to progress such as Projects, Published Books andDeped Guidelines.Lay-out:


Screen Name: 3.0 Profile List Page ScreenFile Name: Profile_lists_page_screens.pngDescription: It contains all of the forms and reports thatare going to be generated by the users of the company such asthe Authors, Employees and Customers. It also holds theProfile lists feature. Layout:


Screen Name: 4.0 Reports Page ScreenFile Name: Reports_Screen_page.png Description: It contains all of the reports that are used inProduction, Progress, Incoming and Outgoing Report. Lay-out:

6.4 Form Specifications

Form Name: Login ScreenDescription: It allows the user to access the application

through checking the system's database if the he/she user isregistered.

Prepared By:Used By:


Volume and Frequency:Layout:

Form Name: Auto MailDescription: It allows the user to access communication

towards the company's employees and authors using anelectronic form.

Prepared By:Used By:Volume and Frequency:Layout:


Form Name: Add Author InformationDescription: Allows the user to add, edit information, and

store an author for the company using an electronic form.Prepared By:Used By:Volume and Frequency:Layout:


Form Name: Add Employee InformationDescription: Allows the user to add, edit information, and

stores an employee for the company using an electronic form.Prepared By:Used By:Volume and Frequency:Layout:

Form Name: Create Employee ReportDescription: Allows the employees to create progress reports

using a electronic form referring to the project's daily status.Prepared By:Used By:Volume and Frequency:Layout:


Form Name: Create Outgoing ReportDescription: Allows the users to insert data in an electric

form in order to add information about the project's status andredirects that information to another person.



Form Name: Create Incoming ReportDescription: Allows the users to insert data in an electric

form in order to add information about the project's status andredirects that information from another person.


Form Name: CalendarDescription: Allows the users to insert data in an electric

form in order to add information about the both schedules andimportant matters. It also has a proofing timestamp that helpstrack both time and date of the given schedule.



6.5 Report Specifications

Form Name: Project ReportDescription: Shows all of the Project's Reports and a

concise description of the files created by providing progress bars and thumbnails.

Prepared By:Volume and Frequency:Layout:


Form Name: Published Book ReportDescription: Shows a concise Published Book Report that

contains all important information from the book such as the Publication Date, Title, Subject of the Book and Grade YearLevel designated for the students.

Prepared By:Volume and Frequency:Layout:

Form Name: Author Lists Detail ReportDescription: Shows a concise report of an Author providing

his/her background information for future references.Prepared By:Volume and Frequency:


Layout:

Form Name: Employee Lists Detail ReportDescription: Shows a concise report of an Employee

providing his/her background information for future references.Prepared By:Volume and Frequency:Layout:

Form Name: Employee Daily Report DetailDescription: Shows a concise report of an Employee

providing his/her progress on the project's status, chapters progress and additional notes for certain errors and sudden

improvements.Prepared By:Volume and Frequency:Layout:


Form Name: Incoming/Outgoing Report DetailDescription: Shows a concise report whenever an Employee

passes a report to an Author, Employee from the company itself or person outside the company or vice versa only with

the consent of his/her signature.Prepared By:Volume and Frequency:Layout:


quatro chapter 6

Documents