Specification based testing
Upcoming SlideShare
Loading in...5

Specification based testing



Specification based testing document for the project Student Information system for Institute of Information Technology, University of Dhaka

Specification based testing document for the project Student Information system for Institute of Information Technology, University of Dhaka



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Specification based testing Specification based testing Document Transcript

  • Assignment on-Specification Based Test Analysis Submitted to- Mohammad Ashik Elahi Course Coordinator SE 605 Submitted by- Group 01 Group Members: BIT 0201, BIT 0207, BIT 0210, BIT 0213 BIT 0216, BIT 0219, BIT 0222, BIT 0225, BIT 0228, BIT 0231, BIT 0234 [Date: 05-11-2012]Institute of Information Technology University of Dhaka
  • Product EnvironmentCustomers:Administrator, Coordinator, Teachers, Students, User.Information:The proposed software product is Student Information System (SIS) for Institute ofInformation Technology, University of Dhaka. It will be used to maintain various studentrecords such as semester enrolment, course enrolment and their attendance history. Teachers willuse the system to give daily attendance of the students and find out the non-collegiatestudents if necessary. S/He can view the date-wise attendance sheet or the overall attendancestatus of each student in his/her course. The students will be able to view their course wiseattendance record. The current system in use is a paper-based system. It is too slow and cannotprovide continuously updated attendance record.Developer Relations:As the development team is confident enough to perform the tasks they took the work verysincerely. The all are friendly to criticize/appreciate our test strategy. The programmers arealways available to take quick initiatives.Test Team:The testing team has been formed within the total project development team where there aresome other guys such as instructor and some specialized who is not included implicitly in thedevelopment team. Especially the writers of the specification and programmers of the previousversion developers are included in the test team. We think we have not enough skilled testingmembers in the development team to fulfill a reasonable test strategy, so training them isimportant to perform the tasks.
  • Equipment & Tools:The development team has the entire hardware requirement to execute the tests as well as theenvironment setup is ready to perform the testing tasks. Some test automation tools are needed toperform the testing like Badboy, Session tester, testlink, mantis etc. To perform the testingmatrices is needed.Schedule:The design of the test will take 30 days with the execution duration for the test plan is 20 days.The tests cases will run repeatedly for regression purposes. The builds will be available for 10days and the user documentation will be partially available during the testing process and finallyavailable after the 15 days of the final development and testing process.Test Items:The main testing part is belonged to the project scope section of the specifications. So, the mainresponsibility is to test those parts of the entire project. The product is obviously available fortesting. The product is not constantly changing and we hope retesting will not be needed. Theproject is functional and reliable enough that we can effectively test the product.Deliverables:The test team will deliver the project test report along with its result for the products differentportions for reviewing. The deliverables are the parts of the product delivery to the technicalteam of the product development. The report will be documented in a paper passeddocumentation.
  • Product ElementsStructureThe code structure is easily available for the testers for testing. The product has a delightful userinterface with having the sections to perform the functionalities which will be very useful fortesting the product. The product documentation, user manual, web link and license agreement aresome collateral element for the product.Functions  The product is based on managing different kinds of users. So common tasks link register, login, logout etc. are some of the basic user management tasks for the product.  The program management option is an important portion of the product. Where there are several program to define link BIT, MIT etc. and there semesters for each year, defining semesters, attach a semester to a year, checking of academic or nonacademic as well as assigning coordinator from the teacher pool to each program.  There are several courses in a semester for a student to be assigned. Admin will define teachers for the courses where the courses also be defined by the admin. A course must have a unique course number. Some courses may be available to multiple semesters. Coordinator will assign one of more teachers to a course. Courses will be attached to a semester, year and program. Students are enrolled to a course with having the option to assign one student to enroll more than one course. One course can be assigned to more than one semester. If a course has no option of having multiple semester then after attached to a course it will be no longer in the available course list.  Attendance management is another function for the product. Here the program coordinator will define a course schedule known as syllabus and the teachers will give the attendance of the students. Coordinator will define class schedule for each course and schedule will be assigned as a weekday link in the routine. Time slot will be fixed for a day to a course. Teacher will give the attendance sheet to a particular course selecting the present students from the list. Teacher can only give the attendance on that day s/he has class. Opportunity of giving the attendance input to SIS will be only for one day. Teacher can’t see the attendance sheet of his/her course when s/he has no class.  The attendance record can be seen by the student and teacher both.
  • DataThere are different types of tables for the databases for the student information system. Thespecification helps to identify the data types along with the project itself to test different datatypes correctly.Platform  External Software: The system is dependent on the windows platform as it is developed using windows technology. Hence windows technology must be implemented at the server side for functioning of the system. There is minimal dependency at the client side.  Internal Components: The system consists of several components to provide functionalities related to result management, distribution and reporting. At the core, there is SQL server Express Edition 2008 R2 running which contains all the data related to results as well as roles of different types of the users in the system. It follows the Model-View-Controller pattern, facilitated by ASP.NET MVC3 Framework. Through this pattern, the services are provided by linking the user interface with the data services which interact with the data storage.Operations  Users: This system is handled by several different users- Admin, Coordinator, teacher, student and general user.  Environment: Windows 7 both 32 bit & 64 bit, database- SQL server 2008 R2, .NET 3.0 or above.
  • Quality CriteriaOperational Criteria  Capability: There are different types of functions which were listed above in the product elements functions section. The capability testing tests the functions whether those are working perfectly or not.  Reliability: To test how much reliable the product is. Index, Creating class schedule, selecting courses, giving attendance and showing attendance as well as maintaining profile can be under the reliability issue as those functions has issue like error handling, safety etc.  Usability: Indeed almost all the function other than the silly functions should be under the usability issue.  Security: Authentication, Authorization, Privacy and Security holes are the main testing criteria for security. In the product the register, login, password reset, maintaining profile, giving attendance is the main security issue.  Scalability: The scalability section of the product can be the course allocation to different user functionality, course management system and so on.  Performance: How fast the product response when launching, logging in or log our, how fast it retrieves information can be a performance criteria for the product.  Installability: The testing item here to identify the system requirement mentioned in the specifications like system requirements, configurations, uninstallation, upgrades etc.  Compatibility: How the application is compatible with other application. How it works with different protocol, database systems are the testing item here in the compatibility testing.
  • Development Criteria:  Supportability: How economical will the product be to provide to users of the product.  Testability: How effectively the product be tested. Does the product have a test plan for testing its functionality?  Maintainability: How economical it to be maintains the product for further failure issue. The other issues for testing which affects the product are portability, localizability etc.