Smart Card System

Extracts from this essay...

Introduction

Chapter 1: Client- Server Technology 1.1 Client-Server Concept and Architecture The term "client/server" implies that clients and servers are separate logical entities that work together, usually over a network, to accomplish a task. Client/server is more than a client and a server communicating across a network. Client/server uses asynchronous and synchronous messaging techniques with the assistance of middle-ware to communicate across a network. Client/Server uses this approach of a client (UI) and the server (database I/O) to provide its robust distributed capabilities. The company, Sigma has used this technique for over 15 years to allow its products to be ported to multiple platforms, databases, and transaction processors while retaining a product's marketability and enhanced functionality from decade to decade. Sigma's client/server product uses an asynchronous approach of sending a message to request an action and receives a message containing the information requested. This approach allows the product to send intensive CPU processing requests to the server to perform and return the results to the client when finished. Sigma's architecture is based on re-usability and portability. Sigma currently uses a standard I/O routine, which is mutually exclusive from the user interface. Sigma's current architecture supports character-based screens and a variety of databases where the user interface is independent of the database access. This architecture corresponds directly to the architecture used in a GUI Client/Server environment. Sigma's client/server product uses an asynchronous approach of sending a message to request an action and receives a message containing the information requested. A traditional client/server application is that of the File Server where clients request files from the File Server. This results in the entire file being sent to the client but necessitates many message exchanges across the network. Another traditional client/server application is that of the Database Server where clients pass SQL requests to the server. The Database Server executes each SQL statement and passes the results back to the client.

Middle

In other words, system, which other than windows might need to undergoes testing with the system and it is quite difficult to provide the same level of quality assurance in this case. The ability of the system to evolve is also needed to take into consideration. However, the adding of the new function or so-called components will need through analysis and this may cause budget increased before any adding could be done. This is mainly because the integration needs great efforts. 6.5 Function-Point Metrics Calculate Measure Parameters Measurement parameter Count Simple Average Complex Number of user inputs 15 X 3 4 6 = 60 Number of user outputs 20 X 4 5 7 = 140 Number of user inquiries 5 X 3 4 6 = 30 Number of files 1 X 7 10 15 = 15 Number of external interfaces 27 X 5 7 10 = 135 Count Total 380 Calculate Functions 1. Does the system require reliable backup and recovery? No 2. Are data communications required? Yes 3. Are there distributed processing functions? No 4. Is performance critical? Yes 5. Will the system run in an existing heavily utilized operational environment? No 6. Does the system require on-line data entry? Yes 7. Does the on-line data entry require the input transaction to be built over multiple screens or operation? Yes 8. Are the master files updated on-line? Yes 9. Are the inputs, outputs, files or inquiries complex? Yes 10. Is the internal processing complex? Yes 11. Is the code designed to be reusable? No 12. Are the conversion and installation included in the design? No 13. Is the system designed for multiple installations in different organization? No 14. Is the system designed to facilitate change and ease of use by users? Yes ?FI = 8 Function Point = Count Total X [ 0.65 + 0.01 X ?FI ] = 380 X [0.65 + 0.01 X 8] = 380 X [0.65 + 0.08] = 380 X 0.73 = 277.4 Chapter 7: System Design And

Conclusion

To test the system. 21 Mac 2001 To document the testing result. To document the valid data. To document the valid data. 22 Mac 2001 To document the testing result. To document the invalid data To document the invalid data. 23 Mac 2001 To produce the testing report. 1. To document the various testing methods that has been conducted by team. 2. To compile the valid data and the invalid data thay has been documented earlier. To produce the project objective report for testing. 24 Mac 2001 Compile the Final Documentation Report To compile all the documentation regarding to the project planning. To compile the project planning report. 25 Mac 2001 Compile the Final Documentation Report To compile all the literature review that has been studied earlier. To compile the literature review report. CSC 566 COMPUTER PROJECT MANAGEMENT WEEKLY REPORT WEEK NO: 13 GROUP NO/NAME: MAXTEC GROUP MEMBERS: Tan She Loo 790620-01-5609 Tan Chin Heng 800718-08-5097 Lau Siew Kong 810803-13-5273 Yap Jian Heung 801228-12-5505 Date ACTIVITY DETAILED REPORT (OF ACTIVITY) REMARKS/ACTION BY GROUP REMARKS/ ACTIONS BY THE LECTURER SIGNATURE OF THE LECTURER 26 Mac 2001 Compile the Final Documentation Report. To compile all the documentation regarding the system requirement specification and design specification. To compile the requirements specification and design specification report. 27 Mac 2001 Compile the Final Documentation Report To compile the entire document for the system. To produce the Final Documentation of the system 28 Mac 2001 To produce the user manual. To document the step-by-step instruction to use the system. To produce the step-by-step instruction to use the system. 29 Mac 2001 Presentation preparation To identify what features should be presented during the demo session. Identifying the features that need to be presented. 30 Mac 2001 Project Submission and presentation 1. To demo the final system to our supervisor. 2. To submit the Final Documentation Report for assessment. 1. To demo the final system to lecturer. 2. Submit the Final Documentation Report. Implementation Of Intelligent Computer Lab Access Control Using Smart Card By Secure And Reliable Cryptography Prepared by MAXTEC December 2000 Session Page: 20

The above preview is unformatted text

Found what you're looking for?

  • Start learning 29% faster today
  • Over 150,000 essays available
  • Just £6.99 a month

Not the one? Search for your essay title...
  • Over 180,000 student essays
  • Every subject and level covered
  • Thousands of essays marked by teachers
  • Over 180,000 essays
    written by students
  • Annotated by
    experienced teachers
  • Ideas and feedback to write
    your own great essays

Marked by a teacher

This essay has been marked by one of our great teachers. You can read the full teachers notes when you download the essay.

Peer reviewed

This essay has been reviewed by one of our specialist student essay reviewing squad. Read the full review on the essay page.

Peer reviewed

This essay has been reviewed by one of our specialist student essay reviewing squad. Read the full review under the essay preview on this page.