Difference between revisions of "IS480 Team wiki: 2017T2 Alpha Finals"
(added in technical complexity-security) |
|||
Line 27: | Line 27: | ||
==Project Progress Summary== | ==Project Progress Summary== | ||
This section will highlight the progress and changes since midterm.<br> | This section will highlight the progress and changes since midterm.<br> | ||
− | <font color = "#2952a3" >'''Final Presentation Slides:'''</font> | + | <font color = "#2952a3" >'''Final Presentation Slides:'''</font> Will be updated by 14 April 2018<br> |
<font color = "#2952a3" >'''Deployed Site Link:'''</font> To access the deployed site link,[http://alphahealth.tk/AlphaHealthWeb/login.jsp <font color = "#0000FF" >'''click here'''</font>] | <font color = "#2952a3" >'''Deployed Site Link:'''</font> To access the deployed site link,[http://alphahealth.tk/AlphaHealthWeb/login.jsp <font color = "#0000FF" >'''click here'''</font>] | ||
* Our project, UroHealth, has a total of 15 iterations. | * Our project, UroHealth, has a total of 15 iterations. | ||
Line 173: | Line 173: | ||
===Deployment=== | ===Deployment=== | ||
− | In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link. | + | <!--In an iterative approach, ready to use system should be available (deployed) for client and instructions to access the system described here (user name). If necessary, provide a deployment diagram link.--> |
+ | <font color = "#2952a3" >'''Deployed Site Link:'''</font> To access the deployed site link,[http://alphahealth.tk/AlphaHealthWeb/login.jsp <font color = "#0000FF" >'''click here'''</font>] | ||
+ | Doctor <br> | ||
+ | Username: TestDoc01 <br> | ||
+ | Password: @TestDoc123! <br> | ||
+ | |||
+ | Administrator <br> | ||
+ | Username: Admin01 <br> | ||
+ | Password: @Admin123! <br> | ||
===Testing=== | ===Testing=== | ||
− | Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc. | + | <!--Describe the testing done on your system. For example, the number of user testing, tester profile, test cases, survey results, issue tracker, bug reports, etc.--> |
+ | This section will be updated by 13 April 2018 (after we have conducted our user testing). | ||
==Reflection== | ==Reflection== |
Revision as of 22:54, 3 April 2018
HOME | OUR TEAM | PROJECT OVERVIEW | PROJECT MANAGEMENT | DOCUMENTATION |
Main Wiki | Midterm Wiki | Finals Wiki |
Project Progress SummaryThis section will highlight the progress and changes since midterm.
Project HighlightsThe following shows the project highlights since midterms:
Project ManagementFunctionalities completed: 100% Project Schedule (Plan Vs Actual)Changes since midterm: Change Management since midterms
Project MetricsTo view the project metrics, click here. Technical Complexity
Quality of ProductProject Deliverables
QualityExplain the quality attributes (non functional) of your project deliverables. Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary. DeploymentDeployed Site Link: To access the deployed site link,click here
Doctor Administrator TestingThis section will be updated by 13 April 2018 (after we have conducted our user testing). ReflectionTeam ReflectionOur FYP journey as a team has been challenging yet enriching & fulfilling. It all begin when our team took up the challenge to enhance patients’ urological healthcare experience, targeted at the elderly (males >= 50 years old). We overcame the uncertainties and unfamiliarity when it comes to empathizing with the elderly in order to enhance the usability of the mobile application to meet their needs. In addition, we experienced and learnt how to manage scope creeps and stakeholders’ expectations while abiding to the hospital’s stringent regulations. As individuals, we acknowledged our personal growth in the technical and project management aspects. Collectively, the experience of delivering a product that fulfills the business requirements is indeed rewarding. Individual ReflectionHui Yee's ReflectionThroughout the phases of the project, I have learnt that interacting with the team and the stakeholders is important in allowing a collaborative environment. As the time goes by, I feel that the role as a project manager has trained me to horn my critical-thinking and decision making skills. Moreover, my involvement in user testing has allowed me to understand that there are different needs and requirements that different age groups look out for. For the project, the application that we are building serves to address the needs of the elderly. Thus, it was an eye-opener for me to be able to witness the elderly' usage of the application, and also think of ways to improve the application UI/UX in order to address their needs. Aloysius's ReflectionAs the Lead Developer, I was in charge in designing and structuring the project architecture. The experience of working with an actual client made the project challenging but introduced a sense of realism to the things you do. Technologies that were implemented needed to be scrutinized carefully, every functionality needs to be specific and useful towards the client's need. Furthermore, I was heavily involved in the development of the React-Native application, being able to develop an elderly-centric medical application was a unique experience, to be exposed to vastly different requirements and situations, really allowed me to challenge myself to develop intuitive functionalities that can be easily understood. One key takeaway would be to really understand your client's persona, with an application for a medical organization, the requirements, the security is immensely different from normal Business-To-Consumer apps. Moving forward, I would place more emphasize and appreciation for the requirements process that will define the rest of the development lifecycle. Jun Ming's ReflectionThe IS480 journey has been a fulfilling one for me that is filled with many learning experiences. When I first started this journey, I was still uncertain of my own skills as a UI/UX designer, as well as a front end developer. Having this opportunity to work on this project enabled me to make use of the skills I've learnt throughout the three years in SMU and my polytechnic years. After working with actual users and clients, I am able to better manage the expectations of the clients and provide a better user experience. As our team is on the final lap, I now come out from this journey as a more confident front end developer that is ready to embark on many more projects in the working world. Carine's ReflectionJeremy's ReflectionHong Ye's ReflectionWhen I first came into the role as a backend developer, I had a clear vision of how the application was going to turn out after speaking to the clients. I felt confident that the project would be smooth-sailing but after several iterations, certain functionality were not as easy as it seem to be. This is mainly attributed by the fact that this system is located within an intranet which had no internet access thus disallowing us from utilizing many API for our functionalities forcing us to search for alternatives. This has taught me that even though most functionalities may have online help to be easily achieved, business constraints could severely affect this and force us to look for alternatives. Having this opportunity to do this project has allowed me to not only demonstrate the skills I’ve been taught in SMU but also learn new things to achieve the client’s requirements, this has also allowed me to experience real-world scenario of changing requirements. Sponsor CommentThis section will be updated by 13 April 2018. |