Iter3 Checker & Manager home pages
- Iteration Goals
- Team Roles
- Task Management
- Total Estimation
- Screen Shots
- Diagrams
- Code review
- Code tests
- Meeting Summaries
- Retrospective
- Client Feedback
- Deployment
- Next Iteration Planning
In this iteration we are planning to create student and teacher home pages, project upload page and secure all pages so that only registered users (according to their permissions) can view the pages
-
- Allow checker to login into the system (US5).
- Allow checker to add project feedback (US16 ).
-
connecting Checker to projects
- Connecting Checker to projects (US11 ).
-
- Allow manager to login into the system (US6).
- Allow manager to create new users (US8).
- Allow manager to view and update competitions (US14).
- Start developing manager tools.
-
- Protect pages, so only allowed users can observe pages.
Remark: You can view our US(User stories) in our SRS document
In this iteration we have divided the work in the following order:
Adi Halali - Responsible for the UI design of the new developed pages. also responsible for alerts for new messages
Moran Zargari - Responsible for creating generic table list view that we will use at the projects view page from the side of the teacher/checker/manager. Although responsible for security
Itay Hefetz - Responsible for the improvement of project upload/update pages and users home pages. Also responsible for the creation of basic checker/manager home pages and responsible for handling repair and upgrades according to customer requirements.
Alex Levenzon - Responsible for the improvement of project upload/update pages and users home pages. Also responsible for the creation of basic checker/manager home pages. Responsible for writing the wiki iteration page.
Igor Kholodenko - Responsible for the development of clock feature that will block users from sending or changing projects after a given period of time. Also made the QA tests.
The current tasks, and their matching iterations and priority can be found in the issues page
The main project Kanban board can be found here
In this iteration our time estimations were not so correct and because of that we left some issues under development, especially the managers home page that we hope that we will finish in the upcoming days. . Most of the time took for learning the development environment and competing injecting dynamic html and js code through jquery in angular - that were new to us.
Before iteration:
After Iteration:
Relevant diagrams to all development iterations can be found at the SDS document
Code review is shared across team members both verbally and through group e-mail. Also, all of our team members are responsible to document their written code after each commit that they made. Product files are divided into corresponding folders , each folder contains different feature or product service - with its corresponding files.
- login as checker
- Notice of a lack of details based on the status stored in Firebase
- Link a teacher to related student projects
- Sending a message by admin
- Receiving the message on the student's message screen
- validation tests
Almost all of our development process is held during our weekly 2-3 days meeting at our college. Working as a team is a great idea and has a lot of advantages. During our development meetings we discuss our tasks, divide them, plan the work and of course - implementing the features of this iteration.
In this iteration the development process was complicated for us and took significantly more time that the second iteration. We managed to finish about 80% of our tasks with a delay of two days. Some features in this iteration still have to be improved and developed. Overall this iteration was really challenging but we think that we coped with the challenges on our best side.
Working as a team, most of the time together, proved itself really well in all aspects and saved us a lot of time not deal with issues that related to under knowledge. If somebody got stuck - one of our team members gave him an extra hand. Also, coping with bugs and fixing then as a team was really useful to our development experience and to the progress of the project. Worse to mention - during the iterations we learned how to use search engines really well - now we can find answers to questions that we have much faster that before - because of the experience that we gained from this course
Completing our tasks on time was the big issue in this iteration. Although the features were not so hard to develop - they are full of small features and parts that we had to develop and check that they all work together well.
Understanding how to work in the correct way with TDD and how to write small tests to check our application was really helpful for us in this iteration.
During this iteration we held a meeting with the customer. We presented to him our current deployment of the website and asked some questions about the features that we developed and will be developed, that were not so clear to us. The customer was really impressed from what we did so far. She gave us some comments about things that she wanted to change and also told us how the feature development should be like and what it should include. You can find the bullet point of the meeting summary here: [link]
Our current alpha deployment is up and running at this link.
Currently this version supports functional features:
- Full user registration
- Login/Logout and password reset option
- Home page with navigation through all available application pages
- Change registration details
- Upload project including user file (This is still under development for full features).
- View and update project details (This is still under development for full features).
- View and update projects in a list view for teacher
- Upload recommendations through checkers home page
- Make some basic management tasks through managers home page
Pages that are still under development:
- Checkers home page
- Managers home page
The fourth iteration planning can be found here
