cis420 final presentation notes

  1. use case diagram
    • - this shows a high level of functionality of our system and those who interact of which parts of the system
    • - 4 users each play a different role
    • - potential customer can become an existing customer when agreeing to services
    • - admin has the most extensive use with the system
  2. Class Diagram
    • - this is a static view of our system
    • - customer, employee, admin class inherit some of the functionality of the system users (superclass)
    • - account history is a aggregations of customer,
    • - meaning if there is no customer then there is no account history
    • - these class diagrams help us eliminate redundant coding
  3. Conceptual Database Design
    - entities, relationships, and attributes are the building blocks for this Conceptual Design

    - entities in our case are objects we want to store data

    - After a strong analysis and design we can move forward to implementation
  4. Implementation
    • - To prepare ourselves for system implementation we have
    • - transferred coding from our localhost to our clients web host server
    • - upgraded servers database management system to a more updated stable version of MyphpAdmin
    • - meaning we have coded our system using myphpadmin version 3.5
    • - using anything before that would make the system unstable
    • - we can also make ourselves available for training, installation, and post installation activities.
    • - with these preparation we are ready for the whole system to go live

    moving one to the next phase of the sdlc
  5. Testing
    • - these are the testing approach we used
    • - Unit test: each individual parts/components of the system in isolated test
    • - the front end. admin, customer logins ...
    • - Integration test: each of those components are tested in larger group and a combination of
    • - System test: the system as a whole was tested . with queries and data inputs
    • - we also did
    • - Regression test: after implementing new features or bug fixes, you re-test scenarios which worked in the past.
    • - Smoke testing: initial test to see if smoke if forming. to see if testing can continue

    - we have also prepared our system for future maintenance if our client chooses to use our system
  6. Maintenance
    • - The purpose of the maintenance phase is to ensure the information system is fully functional and performs optimally until the system reaches its end of life.
    • - with phpmyadmin we can monitor DB with traffic and query statistics
    • - we can monitor front end performance using a webalizer (web analyzer) program
    • - this can show us...
    • - what pages get the most hits, at what point of time was the most traffic.
    • - with the phpmyadmin and webanalizer we can monitor system performance
    • - Once a system becomes operational, we can be available, to ensure that the user needs are continue to be met and that the system continues to perform according to specifications
    • - we can do Routine hardware and software maintenance and upgrades are performed to ensure effective system operations.
    • - we can do User training as needed, to acquaint new users to the system

    I pass it on to dominick and he will show us how we will keep this system secure
  7. Admin Menu Bar
    • - once we have logged in, we get a confirmation that we have correctly logged in
    • - anything else would otherwise give us a error message
  8. New Requests
    • - we can click on the New Request drop down and this gives us a list of new service request from New and Existing customers.
    • - each header is sortable
    • - when we click the submit quote button
    • - we get a form with the appropriate fields populated with the customers data that the system pulls from our DB
    • - we have name, address, phone
    • - as the adim we can review the service request and enter a quoted price
    • - once we push the submit button we get a confirmation that our data is sent and updated
    • - an email will be sent to the customer with the appropriate information and the quoted price
    • - for new customers the email will also include a user name and an randomly generated password that they can use to login and accept the price quoted
    • - when the customer logs in they get a similar menu bar with less features
    • - customer can change username and password at a later time
  9. Pending
    • - when we submit that quote back to the customer the system will drop the request from new and move it to our pending list
    • - this list here are all the service quote sent to the customer, but are awaiting approval or confirmation from the customer - when we click the button
    • - here we can see the pending request we have left an option for the admin to resend quotes or comments to the customer to remind the customer (to have an open line of contact)
  10. Confirmed
    • - once the customer logged on and confirmed the quote the system will then remove it from pending and place it on our confirmed list
    • - this lists all the service request that are confirmed by the customer
    • - we can click here and view the past service request
  11. Generate Service Report
    • - once the service is complete and the job is done the admin or employee can generate a service report
    • - a service report are reports for the customer and company that has all the detail, parts ordered and finding for the service completed
    • - here we can fill out the service date, parts ordered, findings and comments
    • - when we click submit we get a conformation and the information gets stored into the DB
    • - the system again move the report from generation to completed
  12. Completed
    • - this gives us a history of all the service reports completed
    • - the customer can also retrieve this information on their login menu bar
    • - on the customer menu bar will list all service reports pertaining to the customer that has logged on
    • - as opposed to the admin menu will list all reports from all customers
  13. Send Invoice
    • - once the service reports is completed we can send a invoice to the customer for the service rendered
    • - when we click edit invoice we get a form
    • - the system pull the information from the database and populates the appropriate fields
    • - the admin just needs to enter a date and a final price
    • - we give the admin the option to enter a final price
    • - because the final price may differ from the quoted price
    • - there may have been added parts or extra service performed
  14. Completed Invoice
    • - when we click submit we get a another confirmation the database gets updated
    • - an email get sent to the customer stating they have a new invoice they can view when they login and a link is provided
  15. Documents
    • - here we have pdf documents readily available for admin and employees to print out when needed
    • - these are documents that are frequently used and are needed in hard copy form
  16. Web analyzer
    • - here we have a web analyzer, referring back to our maintenance phase
    • - we made this available for our client so he can track page hits and web traffic
  17. Logout
    • - last but not least we can log out
    • - this confirms that our session is ending and we are safely logout
    • I will bring it back to JD and he will conclude our presentation
Card Set
cis420 final presentation notes
cis420 final presentation notes