meljun cortes matrix for endorsement and adviser's monitoring of itc 52 deliverables

7/30/2019 MELJUN CORTES Matrix for Endorsement and Adviser's Monitoring of ITC 52 Deliverables

1/8

JOSE RIZAL UNIVERSITY CO,PUTERIT DEPARTMENTMATRIX FOR ENDORSEMENT AND MONITORING OF ITC 52 DELIVERABLES

(for the Technical Adviser)

Note:The researchers must present the deliverable with an associatedUSE CASE.

COMPONENTS/DESCRIPTION PERCENTAGE RATING REMARKS/COMMENTSI LOG IN FORM (10%)

Registration Page/Sign Up

User name field - the user name of the person who logs in.

Password field the password of the person who logs in.

Log in button - this button will submit the form to the server

Log out Component

Success /Error Handling and Validation

Authentication, Authorization and Management ofAccounts must be observed

10%

RATING Adviser Signature:

Date Checked:

COMPONENTS/DESCRIPTION PERCENTAGE RATING REMARKS/COMMENTS

II FILE MAINTENANCE 25%

1.

Operations that must be involved in the deliverable, others ++The ADD (insert or append) = allows user place new data in ourfile. Depending on the system on development or file system such asfile system versus database file system. This may be placed after anexisting data or at the end of the file even more ( example: ADD NewEmployee)

5%

2.

The UPDATE (edit, modify, change) = allows system user to take

existing data within the text file or database and modify or changethat data.

5%

3.

The DELETE (cease, remove, purge) = allows the system user toremove data in a text file or database. Depending on the value of thedata or of the database itself in the system, users can cease or delete i

5%

4. Success /Error Handling 5%

5.

Validation shall be observedNote: Before the execution in any of the above operations; a ConfirmationDialogue shall prompt the USER if the operation shall be continued orterminated.

5%


ddd/12 Page 1 of8

Title:_______________________________________Group Name: ______________Adviser: ___________


2/8

Date Checked:


III TRANSACTIONS 35%

General Requirement:1. Three Click Policy2. Inclusion of Consolidation (roll-up), drill-down, slicing and

dicing and modeling in the processes.3. Processes must be based on the Data Flow Diagram4. There must be a large volume of transactions to justify the

need of developing the Management Information System5. Inputs and output shall be based on the Requirements

Document.

6. Structures must include hierarchical structure, network

structure relational structure

1. TYPE OF SYSTEM PROCESSING 10%

TRANSACTION PROCESSINGThe system provides and allows pre-defined, structured or a standardtransactions. Each transaction is usually in a minimal duration and theactivity for the transaction is planned or scheduled.

BATCH PROCESSING

System provides transactions or jobs that are processed at the sametime. Series of programs or jobs are executed on the system with nomore than once human or manual intervention. Results, may not beimmediately available, however delay or waiting time must be manage.(Example: Use of Web browsers Add-On e.i. (iMacros of MozillaFirefox, and Web Replay of Internet Explorer)

REAL-TIME PROCESSING

The system should give a guarantee of appropriate response to a user

or system requests quickly enough as a result of user or systeminterventions and constraints. Transactions must be unique; however itshould not be a part of the group transactions. (Ex. SimulatedDashboards, DSP, and RTOS)

TIME-SHARING

System can accommodate sharing of a computer system amongmultiple users giving each user an exclusive control of the system. Theusers may be working on the same page or module, but there areminimal restrictions on the type of work each of the system users isworking on. (e.i. Centralized Computing, LDAP, Online

Analytical Processing (OLAP)

ddd/12 Page 2 of8


3/8

2. TRANSACTIONS MODEL 5%

MODEL DRIVEN; make use of statistical presentation, simulations or

models in presenting and providing a business solution or strategy.

COMMUNICATIONS DRIVEN; system users can use transaction and

tasks dependencies and integrated data to come up with a series of

business reports as a continuous activity of the business solution or

strategy. This model can be in an office environment or on the web; or

a cross-platform using a Web Technology.

DATA DRIVEN; transactions put an emphasis on collected data that

is then manipulated to fit the business needs. This data can be intern-

al, external and in a variety of formats to support the Management

4Ps (People, Process, Partners, Products).

DOCUMENT DRIVEN, transaction uses existing or pre-approved doc-

uments in a variety of data types such a text documents, spreadsheets

and database records to come up with business solutions and initiat-

ives and manipulating data to provide refined strategies

KNOWLEDGE DRIVEN; transactions adopt to special rules, Standard

Operating Procedure, protocols and/or frameworks of the company,

the system and computer or used by a human to determine whether a

solution should be made. These rules and protocols are used to make

the business strategy3. TRANSACTION AND DATA WAREHOUSING 10%

CONSOLIDATED: Organization of data is observed by consistent

naming conventions, syntax and semantics, metrics and measure-

ments and other data behaviour and attributes. It allows management

of data and warehousing from across the organizational needs.

READ-ONLY: Unless the data is incorrect; it should become read-only

once move to the data, hence it must never be updated. Only querying

and loading shall be the operations available in the data warehouse

ddd/12 Page 3 of8


4/8

SUBJECT-ORIENTED; for a medium to a large scale organizations,

large and huge amount of data are stored across organization; how-

ever relevant data maybe irrelevant for reporting requirements. This

method shall organize only key business information from the opera-

tions and shall be made available for analysis.

HISTORICAL/ARCHIVAL: Transaction which represent the current

value at anytime. Transactions shall provide series of reports, snap-

shots, or in any form as an organizational data generated over period

of time.

4. BACK UP AND RECOVERY PROCESSES5%

JOURNALAudit trail of transactions and database changes are maintained usingthe Journal. Transaction and Database change logs are used. Thetransaction log must show the records of all essential data for eachtransactions made, including data values, time of transaction andterminal number or server. A database change log must provide valuesand information before and after values of records that have beenmodified by transactions.

CHECKPOINTTo provide a point of view of data within the database, the systemmay provide a checkpoint. This will serve as reference or identifier ofthe present status of database

RECOVERY MANAGER

A recovery manager is a program or module used to restore the data-

base to a correct condition, and thus can restart the transaction pro-

cessing.BACKWARD RECOVERY

It involves the logic of reprocessing each transaction. It will reverse

changes that has been made by transactions but aborted. It usually

used to UNDO changes made to the database.

FORWARD RECOVERY

The system must be able to back up a copy of database. The transac-

tion will then reprocess according to the transaction journal that has

been made between the time the backup was made and the current

time.

ddd/12 Page 4 of8


5/8

5. TRANSACTIONS FEATURES 5%

PERFORMANCE: System must be able to response even in a data

and network traffic. Performance can be measured by the number of

transactions the system can process in a given period of time.

CONTINUAL SERVICE/USER SUPPORTThe system must be made available during the time period when the

users are entering transactions. System should not disrupt or interrupt

the operation; else researcher shall provide fault-tolerant systems or

module to the end-users. (Ex. When the biometric device is not

working for a Payroll System, employee can still Time-In us-

ing an interface in the system with Username=employee id>

password= firstname.familyname)

EASE OF USE/USER FRIENDLINESS

System users are casual users and with their own language. The sys-

tem should be in a simple form to be used and interpreted. It mustprotect user from data-entry errors and allow them to easily correct

their errors once made, and should serve their purposes alike.

SHORT TRANSACTIONS AND EVENTS

Transaction must be short to achieve quick processing response. This

is employed to avoid concurrency and paces in the systems.

REAL-TIME BACKUP

Schedule should be between low times of activity to prevent lag of the

server.

HIGH NORMALIZATION (at least 3rd Normalized Form)

Redundant information shall be avoided and concurrency must be im-

proved to increase speed and improved back-

ARCHIVING OF HISTORICAL DATA

Uncommonly used data are moved into other databases or backed up

tables. This keeps tables small and also improves backup times.

GOOD HARDWARE CONFIGURATION

Input and output technologies employed in the system must be able to

handle many users and provide quick response times

DATA INTEGRITY

ddd/12 Page 5 of8


6/8

The system must be able to handle hardware or software problems

without corrupting data. Multiple users must be protected from chan-

ging the same data at the same time ( ex. 2 Reservation Specialist

cannot sell the same seat on an airplane for a Reservation

Transaction.)

INTEROPERABILITY AND MODULAR GROWTH

It should be possible to add, replace, or update hardware and software

components without shutting down the system. The system should be

capable of growth at any incremental costs, which does not require the

whole system replacement. Module of the system can be used in other

system as well when needed.


Date Checked:


IV REPORTS (15%)

1.

This deliverable shall follow the Reporting Requirements setforth in the Requirements Document. It must follow theCompany's standard forms and the frequency of generatingthe reports, confidentiality and distribution issues. Reportsmust work in any of the output technologies such as printer,

screen displays or as electronic form

TYPE OF REPORTSSummary reportsDetailed reportsHistorical reportsException reports

5%

ddd/12 Page 6 of8


7/8

2.

FREQUENCY IN THE GENERATION OF REPORTSDailyWeeklyBi-MonthlyMonthlyQuarterly

Annually

5%

3.

CONFIDENTIALITY AND DISTRIBUTION OF REPORTSReports within the TeamReports within the DepartmentReports within the Company

Reports for the Company's StakeholdersReports for to be shared and for Public Use and etc.

5%


Date Checked:


V AUDIT TRAILS (5%)

1.

Audit Trails shall provide; the user and IP address making the change (guest or

registered user name), the date and time they changed it,

the table, field and row that was changed, the after update values, the extension used (within the system, or external), the source (back end, or front end). And etc..

3%

2.

Audit Trails Features must be /able Automatic Notification Non-intrusive Accessible User can purge, cease and Archive Audit Trail Data, etc.

2%


ddd/12 Page 7 of8


8/8

Date Checked:


V GUI DESIGN/ADDITIONAL FEATURES (ADD-ONS) (5%)

1.

This component may bring the system into the top of the linetechnologies by employing of the features below;Use of Widgets and Gadgets

2. Use of RSS Feeds or Really Simple Syndication

3. Use of Push and Pull Technologies

4.Conventional Output Design, and Conversion to severalformats

5.Extensible Style Language Transformation (XML, Search,Selection of Data)

6.Animation (Elemental symbols, Spatial orientation, Transition effects,Alteration effects)

7. Search Engine Optimization (SEO)

8.

Or any form of input and output devices which may deem

necessary in the production of efficient, and effectiveManagement Information System and etc.


Date Checked:


VI ACCEPTANCE TESTING (5%)RATING

Company Representative Signature:

Date Accepted:

OVERALL RATING ________

IMPORTANT DATES TO REMEMBER:

ddd/12 Page 8 of8

Milestones Deadlines:

Log-in Page 10% 1st Week of November Nov. 5 - 9, 2012

File Maintenance 25% 2nd week of November Nov. 12 - 16, 2012

Transactions 35% 3rd week of November Nov. 19 - 23, 2012

Reports 15% 4th week of November Nov. 26 - 30, 2012

Audit Trail / GUI / Design 5% 1st week of December Dec. 3 - 7, 2012

Acceptance Testing 2nd / 3rd week of Decemb Dec. 10 - 20, 2012

90% ENDORSEMENT DATE: January 3 - 9 2013

meljun cortes matrix for endorsement and adviser's monitoring of itc 52 deliverables

Documents