This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
: Leader: Quality Assurance: Communication : Documentation: Localization
: Leader: Communication: Quality Assurance
: Leader: Documentation
Team ITC:
Seng KheangSengly LengSophea ChhunVichet Vireak AingChitsaya Chanesakhone
Team Pace :
Alex ApelbaumThomas AchtemichukChad Brokaw
Team India:
Deepti AroraShweta Mehra
Outsourcing Project Library Management System (LMS)
1/19
Presentation Outline Introduction
Software requirements
Technology overview
Client responsibilities
Interaction and communication
Reviews
Software demonstration
Feedbacks
Software acceptation
Conclusion
2/19
Introduction/Description of LMS
• 2 computers No software specific• Pen and paper filling system• Difficult to search for books
ITC Library description
Constraints in library of ITC
• Open from Tuesday to Saturday • Do the registration to borrow the books• Borrow books on Friday afternoon and Saturday• Students can borrow only 2 books (3 days)• Some books can’t lend
– GUI must be intuitive– User guide for this software– Language using is French– Security
Technology overview/DeveloperUS students (Pace university)
• Languages & Tools– Java 1.5– HTML 4.0– CSS 2.0– Eclipse 3.1.2– Subversion 1.3.1– Trac 0.9.5
• Web Server– Apache 2.x
• Java Servlet Container– Tomcat 5.5.x
• DBMS– MySQL 5.0.x
• Operating Environment– Windows XP Service Pack 2– Mozilla Firefox 1.5 Web Browser
7/19
Client responsibilities
• Requirement phase• Find out all our need• Give our need to developer• Explanation and meeting (Chat and mail)• Validate the requirement document (Wiki)• Posting the blog and survey
• Design phase• Accept or reject the track (Trac)• Validate and feedbacks the design document • Meeting online and discussion (chat and mail)• Survey and blog
• Testing phase• Test the software with the requirement (bug)• Feedback• Software evaluation (USA and Indian students)• Accept or reject the software• US software : http://389.tomchuk.com/servlet/Librarian/• Indian software :
• Interface– Cool and easy to use (Not so attractive)– Easy to find information– Always have a link to the home page (not clear)– Can’t contact the webmaster
• Software– Process is good (short time)– Functions have relationship – Security– No description about the software (Help, Description of LMS)– Have some assumption– Can’t resolve the specials cases in our library
• Accept or reject– Accept 75% 15/19
Feedbacks (2/2)
Indian software • Interface
– Colour is not good looking– Easy to find information– Lost the way to return to Menu of software (sometime)– Each link have clear name and identity– Can contact the webmaster
• Software– Add some good functions, LMS description, Help– Security– Functions work independently– Process isn’t so good (long time)– Assumption– Can’t resolve the specials cases in our library
• Accept or reject– Accept 70%
http://csdb.du.ac.in:8090/library/ROOT1/Main.htm
16/19
Software acceptation
– Comparison
• US Software– Easy to use– Interface is good– Many requirement are completed (75%)– Always have a link to menu
• Indian Software– Easy to use– Interface have more colours– Lost the link to menu – Assumption– Can’t modify or delete the books
– Decision
• US software is better• Should add some information about LMS, ITC, Help, Webmaster• Respect the constraints of LMS 17/19
Conclusion
• Likes– Meeting new people (US and Indian)– Outsourcing experiences (as client)– Real life experiences– Knowledge (Trac, Blogger, Track change in MS-word, Instant
massagers)
• Dislikes– Not all US students join the conference
• Culture– Don’t like working at the week-end
• Difficulty communicating– Time zones, Language, Trac
• Conclusion– Like both sides : developer and client