-
Notifications
You must be signed in to change notification settings - Fork 2
Erida Nurçe
For the final week, the team members were engaged in finishing up all the required workload, so that we could deliver a final document representing the work we have done this far. I divided the State diagram redesigning to Elvi and Giulio so that I could focus on finishing the coding of our software. They had to divide the State Diagrams I had drawn for each actor into state diagrams according to my Activity Diagrams. Jorgel and I revised all diagrams. Jorgel designed the Deployment Diagram, I designed the Component diagram.
This week we redesigned the diagrams and continued coding. I worked on the Activity diagrams, State diagrams and class diagrams. I added new Activity diagrams for the payments, and added a payments class in the class diagram. The other team members worked on the diagrams they previously designed. Me and Jorgel decided to focus on coding and let Giulio and Elvi redesign the diagrams.
This week we presented our project in StartUp Live Tirana. We finished designing the user interface, which Giuliano designed using Photoshop and has uploaded in Views Folder. Jorgel and I created a presentation for the project as well as a business plan on how we plan to generate revenue when this project is deployed. We did some Customer Exploration, studied our Solution in detail, and completed our Business Model. You can find the following in the Detailed Analysis Folder. The whole team worked on redesigning the diagrams according to the Professor's tips.
This week the team was in charge of designing the different diagrams for the ABQ platform.
I designed the activity and class diagrams. In collaboration with Jorgel, we designed the state diagrams. Jorgel redesigned the use case diagrams and ER diagram. Giuliano was in charge of the Collaboration Diagrams. Elvi was in charge of the sequence diagrams. Giuliano and Elvi worked together to design the DFD diagrams.
On the sixth week the group was in charge of completing the Use Cases, Use case diagrams and User Scenarios.
Jorgel was responsible for completing the use cases and use cases diagrams, while Elvi and Giuliano were responsible for writing the user scenarios.
According to the professor's request, I revised the Requirements Specifications document we submitted two weeks ago and restructured it as well as added in some new information, along with correcting any mistakes we might have had before. I added in the newly written part of the documentation, while handling any incorrect statements. I also helped jorgel with some of the use cases.
This week, Jorgel and I dealt with the database needed for the software. We decided to include tables in our schema, one for each of the following: Administrator, User (citizen), Municipality Representative, Tariff, Requests (Kerkesa), Complaints (Ankesa). For each table we also decided on the attributes needed to give the software full functionality, and also designed the ER schema. The document can be found in the Sketches folder. Giuliano designed some sketches for the outlook of the web applications which can also be found in the Sketches folder. The whole team, me included, also watched Symfoni tutorials.
This week I read the legal basis, Ligj nr. 10 112, date 09.04.2009, "Per administrimin e bashkepronesise ne ndertesat e banimit", to get a better understanding of what duties the law assigns to building administrators.
After reaching out to the Director of Building Administrators in the Municipality (Drejtori i Administratoreve te Pallateve, Bashkia Tirane) I set up a meeting with the project coordinator. Together with the group, we met and discussed with her our initial idea and she gave us some valuable suggestions to add into the project such as:
- The option for citizens to file complaints through this web application
- The option for administrators to get certified through this web application
In our group meeting that followed, I drew some sketches of what the web application would look like and how it would function. Later on in the week, I completed the legal requirements and the functional requirements part of our requirements engineering documentation.
After our weekly meeting on Tuesday, we decided we had to switch to another idea for our project, because of having a similar topic with many other groups in the class. Since we were already divided between the Health Application and the Municipality Administrators Web Application in the first place, we decided to pick the latter as our final topic for this project. Thus, I had to talk with the client I had set up a meeting with for Wednesday for the Health App and apologize for cancelling our meeting as well as inform them that our project had been changed. During this week I brainstormed for ideas to add functionality to my initial proposal for the Municipality Administrators Web Application, but decided to wait for feedback from Elvi's and Jorgel's Meeting with the Municipality Representative to have more practical knowledge on what this app should include. Jorgel also distributed the Symfony tutorials so I also studied few of them to get to know how to work with Symfony.
On the second week, having completed our first group meeting, we divided team roles. I was assigned as team captain. Having decided to carry on with the Health Application that I suggested, I volunteered to set up a meeting with a possible buyer of the software we had in mind. Meanwhile, in cooperation with the team we discussed what functionalities we could offer in our software and how to tweak it to better fit the customer I had proposed. Since the buyer managed a Medicinal Lab instead of a Hospital, I thought we should include some more specific services for the analysis they offer. I set up a meeting with the customer and did some research on the field to know what we could offer and have an idea of what the customer could ask from us.
During this first week, I tried to come up with ideas for our future software, which we could discuss in our first meeting. I had the following ideas:
- This web application aims to facilitate services offered by the municipality. Every building administrator will manage the citizens inhabiting the building he manages, with the option to add and remove families. The app facilitates services related to reconstruction permits, parking permits, tax payments, etc.
- A software that manages user information for GSM, E, 3G, LTE coverage, instead of the specific apps they use for each at the moment. The app is also used for call barring, data barring and other services performed by the Public Land Mobile Network Company.
- A mobile app that saves patient details, including health diagnosis and prescriptions. It offers different services for the patient and doctors. A doctor can set the next appointment for his patients, can give them a prescription and assign the pills they need to take and timings. A patient will regularly get notifications when he needs to take a pill, or be alerted when his doctor sets an appointment. He can also request an appointment with a doctor, see his health history, or request an ambulance in case of an emergency.