The Institute of Mindfulness



The Institute of Mindfulness (TIM)  is involved with the development, growth and education of the contemplative practitioners.  This institute caters  for both business and customers and now it is in need of a web platform which can help it to disseminate the information to different particpants in media formats. Therefore, TIM has decided to ask for various parties to send their proposals on how to accomplish this goal. This report loks at portal which is designed to provide support and collaboration to the practitioners.


System Capabilities

  • Haas authentication services which can manage user profiles and secure accounts
  • Allows interaction in a blog format which enables end users to track and document contemplative tasks.
  • It should be support by both mobile devices and web browsers
  • Be able to dividce those who pay versus those who use it for free
  • Capability of streaming and delivering multimedia conent to end users
  • Has technical support tools
  • Incorporate pictue and video editing components

Application Benefits

  • Increased revenue and membership
  • Better mindfulness community due to connection with practitioners
  • Facilitates content consumption in different media formats
  • Even small practitioners are encouraged to join and share what they have on the site


The system will have different sections for donating members and for free members. This will

The system will be divided into different level of support for free and donating members. This way more personal services and higher end features can be offered can be divided accordingly.  This will entice more people to become members to continue to strength the financial position of the site for reinvestment and ongoing support.





  1. Discover and analyze of TIM needs
  2. Interview stake holders, Members of the board, the part time volunteer, and participating practitioners
  3. Identify the information types that needs to delivered via the site
  4. Identify the use cases for the tech services
  5. Develop workflows for the sites to enable these services
  6. Design the components of the solution
  7. Design the database tables for capturing member information
  8. Design site plug ins for support and layout and screens
  9. Design/Select the platform to deliver the support and content to end users
  10. Design details of content and collaboration

III.  Program the system

  1. Create the database.
  2. Create the support page
  3. Create the subsequent pages with member and non-member options
  4. Test it and use it
  5. Test the operation of the website
  6. Test the content delivery systems for various forms of media on multiple devises
  7. Select several stakeholders to participate in a beta test

D2-1 Use Cases

  • Enable social networking for practitioners
  • Empower end users to be able to post and stream content
  • Provide technical support options to contributors
  • Provide tools to consume, stream, and various types of media







Consumer User
Business User
Administrative User
Content Contributor
Content Viewer






End user needing support on a posting or site function
Posting content to share with the community
Viewing content about topics





D3-1 – Social networking to find practitioners on key topics

  1. Navigate to Support Page
  2. Log in
  3. Enter and submit ticket
  4. Ticket routes to technical support to address issue



The user will use the top menu or the navigation to access the Tech Help Web Page. In the content area, the Login In will be placed for the user to enter the credential data, and then display content specific to the credentials. View tickets will be display in the content area as well. The Header, Top Menu, and NAV will be existed in every page.  






Table: UserAccounts Table: Ticket
userID: string, auto-increment, {key}

firstName: string {index}

lastName: string

phoneNumber: string

address: string {index}

city: string

state: string

membershipLevel: string

ticketID: string, {key}

userIdD: string, {foreign key}

ticketCatagoty (string)

ticketStatus (string)







D4-2 Desktop or Browser



  • More control over experience
  • Single user experience


  • Significant costs to support multiple operating systems
  • Significant costs to create software updates and patches to multiple form factors
  • Eliminates end user from being able to access anywhere
  • Limits device support based on resources



  • Access from any device
  • Similar experience across multiple platforms
  • Ability to provide content to more people
  • Lower cost of support


  • Requires multiple browsers to support
  • Security will require more investment
  • Requires more costs to support
  • Requires more resources to support



D5-1 Programming Approach

The recommended language would be HTML5 to enable support on multiple platforms and devices. This would make our recommendation Browser based for the above decision.  The end users will come from all walks of life and we will have limited resources to keep up with and maintain various desktop based applications with the ever changing mobile market space. This will keep our costs down and still allow for us to deliver a quality experience to the end user.

D6-1- Testing Approach

Program Testing

  • Limited to own knowledge and experience of portal and media usage
  • Tends to use in the fashion intended
  • Doesn’t have firsthand knowledge of the content that will be uploaded
  • Does not have broad enough scope to think outside of the box


  • Can present different use cases not thought of
  • Can test actions not previously planned for
  • Tends to make mistakes or try uses of media not planned for in design
  • Can test based on actual usage instead of estimated
  • Can present items that cause scope creep


D6-2 – Deployment Issues

Browser Based Application Selected

  • Server operating system
  • Hosted or on premise solution
  • Hardware and network requirements
  • Database software
  • Content delivery platform
  • Content storage and backup
  • Browser consumption issues
  • Security issues
  • PCI compliance issues and auditing
  • Application conflicts

D6-3 – What Other Issues Need to be Addressed to Deploy

  • Security and PCI compliance
  • If it should be hosts by TIM or with an IAAS provider
  • Browser compatibility and support
  • If Domain is available