1. Hito-Shura Milestone 2 presentation Harlan Broughton Stephen Link

2. What is it? Web based management system created by Gregory Newell, Karl Schwirz, and Boleslaw Pawlowicz who are 2009 Uconn Alumni. Hito-Shura is an anime character, not any sort of official name for this sort of web- based system.

3. Why are we doing this? It will actually be used by the marching band to help keep synchrony among members. To gain the experience of working with someone else's code.

4. Current specs Users will be able to access HS through a standard web browser whereas developers will design and implement HS using Visual Studio. The IMS is broken down into six sections: Registration Login Data Access, Members-Only, Notification Pep-band Scheduler,

5. Site map Home ◦ Register ▪ Home ▪ activationPage ◦ Log In ▪ Home ◦ Notification ▪ Home ◦ Pep-band Scheduler ▪ CalendarPage ▪ GameInfoPage ▪ GameSlotPage ▪ AdminPage

6. Signing in The sign-in page features two text fields where the user enters their UCMB user name and password. When matching information is provided the user is logged in and given access to corresponding appropriate information. The user is directed to the Members Registration Page if they do not log in to a preexisting user account.

8. More sign in information Should a member forget their password they may select the 'Forgot Password' link to send the password to the email listed with the user name being requested. Once logged in users may view the current roster of members in the UCMB at the Data Access page. The user will be presented with multiple text boxes (name, section, Uconn classification, etc) which can be filled in to request information about the member or group of members. If a member would like to edit information on their profile they may click 'Edit My Profile' which links to a page providing this functionality. Upon loading the Edit User Account page users will be presented with drop boxes containing all available fields with editable information.

9. Notification system The notification subsystem serves as a tool for communication between members of the band. It allows members to send messages to the email addresses given by other members. Sending these notifications is a privilege given by the administrator.

10. Notification system

11. Pep-band scheduler The pep-band scheduler is only accessible to users who are associated with a pep band in the current year. The scheduler helps both pep-band and administrators deal with attendance of pep- band games, and is contained within three pages: the calendar page, the game page, and the game slot page. The calendar displays every game associated with the band of the logged-in user. Due to the amount of data, the game info may not display and the buttons may be momentarily disabled. Arrows allow movement between months, and there is a link to go to the page for a specific game.

12. Pep-band scheduler Clicking on events will allow members to register to unregister.

13. Event registering

14. Shared Media Administrators have the ability to upload certain media for all members to see, such as past band performances or whatever else they deem appropriate. All members can see the media, but only admin can add or remove them.

15. Shared Media

16. Goals First task is to set up a working server to host everything. Create a fully encrypt the database. Lots of personal information is kept that is needed to be encrypted in order to actually implement this system.

17. Goals Working media section. Currently it is not in a usable state. We will make it fully operational with more features such as: ◦ Comments by the administrator posting. ◦ Comments by members (optional) ◦ Allow users to save certain media to their own computer.

18. Goals Integrate File maker to make the database easier to manipulate. ◦ This will make everything look more professional and neat.

19. Goals General features ◦ Add custom color scheme for users similar to huskymail. ◦ Help system to answer simple questions. ◦ Enable user timeout in which idle users will be logged out automatically.

20. Workload distribution Questionable ◦ A lot of new stuff for both of us, so we are unsure of how much work is needed to complete these tasks. ◦ Harlan will deal with server aspect and aesthetics ◦ I will do more hard-coding, and ideas.

21. Questions?