Redevelopment of MSIA website Project

1
Redevelopment of MSIA website Project

• 
  Presenters
• Supriya Shrestha
• Naresh B. J.
• Praveen K. D.
• Sheng li

2
Client

• Organization
• Medical Software Industry Association (MSIA)
• Representative
• Ms. Hazel (MSIA Secretariat)

3
MSIA

• An association representing healthcare software
  providers
• an official voice for the industry
• negotiates an important changes with government
  and other stakeholders
• Currently hold static informative website

4
Problems with current website

• A static website
• Only provides an information on MSIA
• Does not perform any activity online
• Activities are performed offline manually
• Membership has increased by 50 in last 12 months
• Even Offline registration of membership

5
Project

• Develop a dynamic website
• Website should performs most of the activities of
  MSIA online

6
Functional requirement

• Intended website should
• Have online registration of membership
• Have online renewal of membership
• Have online update of members details
• providing information on
• Recent news
• Upcoming events
• Provide flexibility to visits its members
  website
• Allow to provide feedback

7
Functional requirement (Continue)

• Membership Registration and Renewal should be
  approved or rejected by administrator.
• Those application and feedback is sent to admin
  page as an email.
• Admin should be authorized to delete members,
  events, news and feedback
• Members and administrators section should be
  protected through password verification

8
Non-Functional requirement

• High Performance
• Browser independent fast loading
• Security
• Username password
• Only admin will have rights to manipulate
  database.
• Websites quality
• Industry standards, User friendly low error
  rate
• Hardware Constraints
• Server hardware constraints
• Client Hardware constraints

9
Architecture

• Three tire architecture

10
Deployment Diagram

• DMZ Demilitarized Zone (Extra layer of security
  for LAN)

11
Link Flow Diagram
12
Use case diagram
13
Database Diagram
14
Assumptions and constraints of database

• Administrator will hold information on an
  individual person.
• Member will hold information of an organization
• Administrator may or may not create new
  administrator. But new administrator must be
  created by existing administrator.
• Events and News details should be managed by
  administrator only.
• Members must be approved or rejected by
  administrator.
• A member must have a product and a product must
  be owned by a member.
• A member may have many products. Similarly, a
  product may be owned by many members.
• Administrator may or may not receive feedback.
  But if there is a feedback then it should be sent
  to administrator.

15
Class Diagram
16
Interaction Diagram

• Sequence Diagram for Add event

17
Interaction Diagram

• Sequence Diagram for Update Members details

18
Prototype

• MSIA websites Prototype
• http//localhost/MSIA/Home.aspx