HeaderSIS.jpg

IS480 Team wiki: 2011T2 Panacea: Project Midterm

From IS480
Jump to navigation Jump to search
Panacea Midterm Wiki Logo.png
Midterm Wiki Page

Back to Main Page

Mid Term Slides

Mid Term Slides: Panacea Mid Term Slides

Project Progress Summary

Progress Description

Our team has been progressing at a slow but steady pace since our acceptance. In Mid-January we encountered a major obstacle, which is that our client requested a change of requirements in that he no longer wanted a locally deployed Web Application but instead wanted a Standalone application to be developed instead. This affected our progress greatly because most of our application development prior to January was done in JSP pages. Now, we had to adopt a new framework and change all our development work to a Java Swing framework.

As such, we had to delay our development and greatly reduce our project scope and list of functionalities, as well as redirect the focus of our project. Also, all our prior risk management would have to be done over again, as well as our metrics and our project schedule.Even so, we are confident of having 25% of the basic functionality live by midterm. Even though this is greatly behind our initial planned schedule, we believe that we still be able to finish the application by the end of the term.

Project Highlights:

  • Client Changed requirements, requires us to use Java Swing instead
    • Project Risks greatly increased, as only two of our members were familiar with Java Swing
  • Reduced project Scope
    • Removed Accounting and Finance Module
  • Re-direct focus to be on User Interface

Back to Top

Project Management

Project Schedule and Status (Plan Vs Actual):

Project Schedule Page Download our full project schedule here (open in excel)

Back to Top

Project Metrics:

Project Metrics Page

Back to Top

Project Risks:

Risks and Mitigation Strategies

Back to Top

Technical Complexity:

Ranking Description Actions
1 New Framework and Scope, to understand Java Swing and how to make use of the Swing Model-View-Controller architecture Read up on training documents, search for online resources
2 Tough to understand what makes a good User Interface Design, even with the help of Usability Engineering slides and textbook Constantly thinking of ways to refine the application's User Interface since our focus of the project is on Usability
3 Customizing the framework with our initial database Relatively Doable
4 Develop an application in Java Swing Netbeans is a good and easy way to make use of Java Swing

Back to Top

Quality of product

We have been able to come up with a design for our application that is both easy to manage and understand by making use of the Java Swing Model-View-Controller Architecture. The application has two major components: Front End and Back End.

The Front-End of our application (i.e. the User Interface) controls the navigation of our application and the overall look and feel of the application. The views control how data is presented to the user and determines how users will interact with the application. Customization of the user interface is done using the Java Swing's GUI tools. Interactions with the Views will then be routed to the controllers which are the back-end business logic to decide what is to be displayed.

By making use of Java Swing, what we can achieve is a lightweight UI which is highly customizable and configurable. Moreover, we will be able to guarantee that the graphical objects will look the same on every computer that the application is run on. Also, the application will highly likely be extended beyond its currently planned functionalities and the usage of Java Swing would mean that the application is easily extensible. Also, what we hope to deliver to our client is an application with a pleasant, professional, straightforward and easy to use look and feel, which we believe can be achieved by using Java Swing.

The Back-End of our application is to control the business logic of the application, and determine what data is routed to the front end based on user interactions with the front end. The work is done by our controllers which will interact with our database as well, in storing and retrieving values.

This model-view-controller architecture has helped us to achieve a much more flexible user interface, and has helped in our project scheduling in that tasks on the back end and front end can be accomplished concurrently.

As for the deliverable to our client, it has been highlighted to us that our project will be a proof of concept based on usability. As such, the functionality has to be working well ultimately, but the user interface must be excellent and has to show a great improvement over other clinic management systems out in the market. An easy comparison would be to look at our client system screenshots and comparing them to our current application. It is clear that the User Interface has been greatly improved.

Back to Top

Intermediate Deliverables:

Deliverables

Stage Specification Modules
Project Management Project Minutes Project Documents Repository: Team, Client and Supervisor Meeting Minutes
Project Metrics Project Metrics: Bug and Schedule Metrics
Project Schedule Project Schedule Page: Project Schedule, Timeline, Progress, Status and Archived Project Schedule
Requirements Storyboards Storyboards Page
Existing System Screenshots Client System Screenshots
Analysis Use case Use Case Diagram
Functionality and Business Process Functionalities and Business Processes
Screen Shots

Client System Screenshots

Current Application Screenshots

Design Database Design Documents Database Design Document

Logical Diagram

Logical Diagram (Table)

Paper Prototype Images and Video Recording in Construction
Usability Planning Usability Test Design Document
Testing User Test User Test 1 Test Document

Testing:

We have recorded our first User Test for our Application. View our results and details of the test at our User Test Results Page

Reflection

Team Reflection:

We managed to reschedule our current project schedule to take into account the changes in our requirements. We did so by reducing the scope of our project. However, one thing that really helped was that we planned a lot of buffer days in our initial project schedule, which made rescheduling much easier.

We are currently training in Java Swing by taking notes from a Java Swing Tutorial that we found online. Also, to understand better the architecture and MVC framework that Java Swing offers, we have been looking information on the web. We have shared our resources in the IS480 Knowledge base.

Chula Sulagaesuan

  • Back End Coding is a headache
  • Need to maintain code structure to allow codes to work with each other

Mervin Yong Wei Yang

  • Learning Java Swing is tough, Alot of Project Documents have to be tracked constantly
  • Tough to Match clients' requirements with project

Neo Yi Wen

  • Front End Designing and UI Coding is very taxing
  • Integrating the Front end and Back end gets tougher as complexity of functionalities increase

Tan Junlong

  • Change of project requirements changes the schedule drastically
  • Time management is essential for the project

Supervisor Reflection

Benjamin Gan Reflection

Back to Top

Midterm Reviewer Feedback

Summary of Pointers

Prof. Li Yingjiu

  • The Project is behind the original schedule
  • Project Scope has been reduced by taking out certain functionality due to change of sponsor requirements
  • Focus is on improving the level of usability and the UI
  • The Team needs to make good progress in the next two weeks to catch up, complexity of project seems to be coming from learning Java Swing
  • Both quantitative measures and qualitative measures are used in user testing, but has not been conducted on client side yet
  • Demo only a few features, many incomplete

Prof Kevin Steppe

  • Project Schedule is vague, doesn't seem at all concerned by crashing the project schedule
  • Most of the system is a big CRUD thing, lost 2-3 weeks due to change of scope
  • Average system, fine but not impressive
  • Amount of work done is not much, a good deal of work ahead
  • Demo and Deployment is limited due to a major scope change, need to see more integration to get an idea of what the system can do
  • Answer questions directly, don't cover up issues

Back to Top

Action Plan for Major Comments

  • Fine but unimpressive project / Most of the system is just a big CRUD thing:
    • Considering the progress up to date, we might increase the scope again
    • Want to integrate the Accounting and Finance module again, afterall, FYP(IS480) is about slogging it out, we need to set our sights higher
  • Complexity comes only from learning Java Swing
    • Need to highlight that a good user experience is hard to achieve and we need to focus on this as our project complexity and x-factor
    • Need to highlight more on what is the real complexity and that is to improve user interface
  • Not worried about crashing project schedule
    • Change project manager to push more on project progress
    • Using new tools like teamworkpm to improve progress tracking
  • Need to see more integration to get a better idea of what the system can do
    • After finishing Patient, Search, Medicine and Order module, we will try to schedule a demonstration of the system with both Prof Kevin Steppe and Prof Li Yingjiu to show them a better picture of the system
    • Aim to complete this in 2 weeks time

Back to Top