Date- 27.4.2007
friday
Time- 17:00-20:00
Attendance- All present
Group leader- Vivek Jain
MoM- Luma.S.Kurup
Agenda- A relook at the whole project. Report and presentation formation.
A hectic day it was. Just after our first end term exam today, we were back in action. Enthused we were, as we felt our weeks of hard work is finally fructifying. The countdown for the presentation has begun. We looked at the whole project once again We reviewed the interfaces and architecture diagrams, collated them and started preparing the report. Report got ready by 8 pm. Meanwhile we started working on presentation too. By 10 PM we were ready with the report and presentation.
Friday, April 27, 2007
Minutes of the meeting held on Tuesday (24/05/07)
Time: 9:00pm to 1:00am
Attendance: All Present
Team Leader: Luma s kurup
Minutes: Vivek Jain
Group discussed the various cases that can be tested in the system.
Expected and observed results were discussed for each individual case.
Each group member then created the test plan for his respective module.
Finally all test plans were compiled to form one test plan for the complete system.
Group then discussed the HCI for various modules.\
Different HCI were for each module by respective team members.
One final HCI for the complete project was then created by integrating various HCIs.
Attendance: All Present
Team Leader: Luma s kurup
Minutes: Vivek Jain
Group discussed the various cases that can be tested in the system.
Expected and observed results were discussed for each individual case.
Each group member then created the test plan for his respective module.
Finally all test plans were compiled to form one test plan for the complete system.
Group then discussed the HCI for various modules.\
Different HCI were for each module by respective team members.
One final HCI for the complete project was then created by integrating various HCIs.
Thursday, April 19, 2007
MoM for the 8th meeting held on 19th April
DAY & TIME: 9:00P.M – 11:00 P.M 19.04.2007
ATTENDANCE: All present
GROUP LEADER – SACHIN GUJRATHI
MoM PREPARED BY – RAJEEV JAIN
Agenda: Architecture Diagram
The group discussed the architecture diagrams in today’s meeting. The discussion mainly concentrated on the interactions between the different layers. The group then finalized on the deployment diagram to be made by taking into consideration all the interactions between different subset of the system.
The group also reviewed the class diagram that the group finalized in the previous meeting. The group finally discussed about the HCI to be designed for the project.
ATTENDANCE: All present
GROUP LEADER – SACHIN GUJRATHI
MoM PREPARED BY – RAJEEV JAIN
Agenda: Architecture Diagram
The group discussed the architecture diagrams in today’s meeting. The discussion mainly concentrated on the interactions between the different layers. The group then finalized on the deployment diagram to be made by taking into consideration all the interactions between different subset of the system.
The group also reviewed the class diagram that the group finalized in the previous meeting. The group finally discussed about the HCI to be designed for the project.
Wednesday, April 18, 2007
Minutes of the seventh meeting held on 17th April
Time: 9.45 pm to 12 pm
Attendance: All Present
Team Leader: Rajeev Jain
Minutes: Balaraman
Agenda: Class Diagram
The group initially spent some time in understanding "what is a class?" by going through the course ppts and the web in general. Then the classes pertaining to our system were identified.
Then the subgroups dealt with their respective use case diagrams and came up with the class digrams. This was to bring out the asssociate relationship and how classes interact and the visio software was again used for this
Later after collating all the class diagrams attributes and methods pertaining to each class were identified and listed usin visio.
The group decided to meet two days later to discuss about GUI and physical architecture
Attendance: All Present
Team Leader: Rajeev Jain
Minutes: Balaraman
Agenda: Class Diagram
The group initially spent some time in understanding "what is a class?" by going through the course ppts and the web in general. Then the classes pertaining to our system were identified.
Then the subgroups dealt with their respective use case diagrams and came up with the class digrams. This was to bring out the asssociate relationship and how classes interact and the visio software was again used for this
Later after collating all the class diagrams attributes and methods pertaining to each class were identified and listed usin visio.
The group decided to meet two days later to discuss about GUI and physical architecture
Tuesday, April 10, 2007
MoM for the 6th meeting held on 12.04.2007
DAY & TIME: 9:00P.M – 3:30 P.M 10.04.2007
ATTENDANCE: All present
GROUP LEADER – BALARAMAN R
MoM PREPARED BY – VIVEK JAIN
Agenda: Use Case and Activity Diagram
In our Thursday meeting, the group discussed the use case diagrams at both system level and separate module level.
Group also discussed primary actors, stakeholders and normal flow of events for different modules.
We then decided on how to go for activity diagrams for each use case diagram.
Each group within our group then prepared their respective use case and activity diagrams with proper flow of information from one stage to the next.
Group then finally discussed the possible sub flow or extension of already decided placement activities. The group also discussed upon the class diagrams which is to be covered in the next meeting.
ATTENDANCE: All present
GROUP LEADER – BALARAMAN R
MoM PREPARED BY – VIVEK JAIN
Agenda: Use Case and Activity Diagram
In our Thursday meeting, the group discussed the use case diagrams at both system level and separate module level.
Group also discussed primary actors, stakeholders and normal flow of events for different modules.
We then decided on how to go for activity diagrams for each use case diagram.
Each group within our group then prepared their respective use case and activity diagrams with proper flow of information from one stage to the next.
Group then finally discussed the possible sub flow or extension of already decided placement activities. The group also discussed upon the class diagrams which is to be covered in the next meeting.
Sunday, April 8, 2007
MoM of the 5th meeting held on 07.04.2007
SATURDAY 07.04.2007
TIME – 6.30 TO 7.30 PM
GROUP LEADER – VIVEK JAIN
MoM prepared by - LUMA S KURUP
Agenda- Use Case and review the previous work.
The additional module discussed in the previous meeting was included in the Use case diagram. The connection between the actors and the database was explained in the use case diagram. The implementation of scheduling of placement representatives visit for the pre-placement process was incorporated.
The group divided the different modules amongst the team members. Balaraman and Luma worked on web based poll for deciding allotment of the companies and scheduling of companies both day and time.
Sachin and vivek implemented the checking of schedule by every student and the schedule for placement representatives while visiting companies.
Rajeev worked on preplacement and postplacement online training, emailing students about their selection and creation of forums for summer internships feedback and discussion.
The consolidated and the revised document was created after each team members completed their tasks. At the end it was decided that the group will study the activity diagrams,which is the action item for the next meeting.
TIME – 6.30 TO 7.30 PM
GROUP LEADER – VIVEK JAIN
MoM prepared by - LUMA S KURUP
Agenda- Use Case and review the previous work.
The additional module discussed in the previous meeting was included in the Use case diagram. The connection between the actors and the database was explained in the use case diagram. The implementation of scheduling of placement representatives visit for the pre-placement process was incorporated.
The group divided the different modules amongst the team members. Balaraman and Luma worked on web based poll for deciding allotment of the companies and scheduling of companies both day and time.
Sachin and vivek implemented the checking of schedule by every student and the schedule for placement representatives while visiting companies.
Rajeev worked on preplacement and postplacement online training, emailing students about their selection and creation of forums for summer internships feedback and discussion.
The consolidated and the revised document was created after each team members completed their tasks. At the end it was decided that the group will study the activity diagrams,which is the action item for the next meeting.
Saturday, April 7, 2007
Minutes of the fourth meeting held on Wednesday (04-04-07)
Time: 9 pm to 12 pm
Attendance: All Present
Team Leader: Sachin Gujrathi
Minutes: Rajeev Jain
Agenda: Function Point analysis and Feasibility analysis
Meeting was started reviewing the initial scheduling steps prepared during the Sunday meeting. The steps were analyzed and discussed once more to get everyone on same thinking track.
Later Sachin and Rajeev explained what steps have to be identified (i.e. explaining how software will interact with database for getting data and then the GUI will get info from user). This was done so as to identify various interactions that would take place in each step of scheduling.
After this initial explanation, various steps for scheduling were internally divided among us and every member started identifying the interactions involved in each step. Once this was done, the group as a whole classified the various interactions for function point analysis and then the lines of code and man-hours were calculated.
Once this was done, with the interactions being already identified, we were able to do operational and economic feasibility. Vivek and Luma worked on economic cost part, listing the various software and hardware required and finding the relevant price from the internet. Balaraman worked on operational feasibility simultaneously.
Sachin and Rajeev documented the function point analysis done.
Group wound up with finalizing the ppt for presentation of feasibility and function point analysis.
Attendance: All Present
Team Leader: Sachin Gujrathi
Minutes: Rajeev Jain
Agenda: Function Point analysis and Feasibility analysis
Meeting was started reviewing the initial scheduling steps prepared during the Sunday meeting. The steps were analyzed and discussed once more to get everyone on same thinking track.
Later Sachin and Rajeev explained what steps have to be identified (i.e. explaining how software will interact with database for getting data and then the GUI will get info from user). This was done so as to identify various interactions that would take place in each step of scheduling.
After this initial explanation, various steps for scheduling were internally divided among us and every member started identifying the interactions involved in each step. Once this was done, the group as a whole classified the various interactions for function point analysis and then the lines of code and man-hours were calculated.
Once this was done, with the interactions being already identified, we were able to do operational and economic feasibility. Vivek and Luma worked on economic cost part, listing the various software and hardware required and finding the relevant price from the internet. Balaraman worked on operational feasibility simultaneously.
Sachin and Rajeev documented the function point analysis done.
Group wound up with finalizing the ppt for presentation of feasibility and function point analysis.
Monday, April 2, 2007
Minutes of the third meeting held on Sunday (01-04-07)
Time: 20 30 to 00 45 hrs
Attendance: All Present
Team Leader: Luma S Kurup
Minutes: Balaraman
Agenda: A relook at our objectives and analyse the nitty gritties involved in achieving them
We decided finally it was time to get into details from our suface surfing. This was also essential and a prerequisite for our technical feasibility.
We started off with the underlying objective of minimizing human intervention as elimination of the same is impossible and unnecessary. Bala came up with the way the students can interact with the system (basically a poll) so that the allocation of companies to Day 0,1,2 and 3 is decided. Sachin and vivek then mentioned the minor details required like the inputs to the system such as uploading list of companies, restriction on maximum number of day 0,1,2,3, companies for each student etc.
Based on the above data an initial schedule is generated and sent to companies with sessions indicated after which they can come up with their preference leading to a revised schedule. At this point the group understood how dynamic the entire process can be and then resorted to stopping with a starting solution alone.
Bala, luma and rajeev then decided on the feasibility of student scheduling when students have clashing interviews. A software for this was also discussed about. For this preference of the students (attend/not) for every company will be given.
Rajeev came up with the idea for the brief internship report which can be maintained with the help of forums/ threads.
Vivek then suggested how a webpage can be developed to upload results which can also automatically send emails/ messages to sydents about the results.
The group also decided to scrap certain objectives like alumni interaction (as sriram group is doing it), company details (gaurav vishal group is doing) and allotment of comapnies to placement reps (rather a very simple one and no need for a software help). Action items for the next meeting included function point and feasibility analysis.
Attendance: All Present
Team Leader: Luma S Kurup
Minutes: Balaraman
Agenda: A relook at our objectives and analyse the nitty gritties involved in achieving them
We decided finally it was time to get into details from our suface surfing. This was also essential and a prerequisite for our technical feasibility.
We started off with the underlying objective of minimizing human intervention as elimination of the same is impossible and unnecessary. Bala came up with the way the students can interact with the system (basically a poll) so that the allocation of companies to Day 0,1,2 and 3 is decided. Sachin and vivek then mentioned the minor details required like the inputs to the system such as uploading list of companies, restriction on maximum number of day 0,1,2,3, companies for each student etc.
Based on the above data an initial schedule is generated and sent to companies with sessions indicated after which they can come up with their preference leading to a revised schedule. At this point the group understood how dynamic the entire process can be and then resorted to stopping with a starting solution alone.
Bala, luma and rajeev then decided on the feasibility of student scheduling when students have clashing interviews. A software for this was also discussed about. For this preference of the students (attend/not) for every company will be given.
Rajeev came up with the idea for the brief internship report which can be maintained with the help of forums/ threads.
Vivek then suggested how a webpage can be developed to upload results which can also automatically send emails/ messages to sydents about the results.
The group also decided to scrap certain objectives like alumni interaction (as sriram group is doing it), company details (gaurav vishal group is doing) and allotment of comapnies to placement reps (rather a very simple one and no need for a software help). Action items for the next meeting included function point and feasibility analysis.
Tuesday, March 27, 2007
Sunday, March 25, 2007
Feedback
Leave your comments/feedback here. Your suggestions about placement process are also welcome!
Project - Automation of Placement Process
Objective:
To develop a comprehensive software package that includes among others Company scheduling, Pre-placement online training and Data mining of various placement information with respect to DoMS by Week 16.
To develop a comprehensive software package that includes among others Company scheduling, Pre-placement online training and Data mining of various placement information with respect to DoMS by Week 16.
The purpose of the software package would be–
- Generation of Schedule for interviews during placement season to avoid clashes.
- Scheduling ‘lateral placements’/Summers process
- Placement track record/Data Mining (Brief report on Student’s Summer internship, company details, contact person, timing)
- Allocating companies to placement reps (dividing in terms of broad areas)
- Scheduling Preparatory training course/Orientation program (International recruiters) / PDP / Developing effective resumes / mentoring by alumni
- Messages / Emails to students about offers/selection/salary
Out of Scope of the project –
- Limited only to DoMS
- No candidate profiling
Team Members -
- Sachin Gujrathi
- Rajeev Jain
- Vivek Jain
- Balaraman R
- Luma S Kurup
Welcome All.....!!!!
Hi All,
Welcome to the System Analysis and Design (SAD) blog of group-1. Visit and comment regularly to participate in the discussions.
Welcome to the System Analysis and Design (SAD) blog of group-1. Visit and comment regularly to participate in the discussions.
Subscribe to:
Posts (Atom)