CS708 Software Requirement Engineering Academic Research Paper Assignment No. 01 Solution Fall 2015 Due Date Feb 12, 2016
CS708 - Software Requirement Engineering Academic Research Paper Assignment No. 01 Solution Fall 2015 Due Date Feb 12, 2016
Academic Research Paper Instructions
As part of your course grading, you are required to submit an academic research paper during the semester. This exercise is meant to inculcate in you the research temperament and skills by carrying out a deep study of any research topic/area relevant to this course. You may choose any topic, of your interest, relevant to the course. Following are the details of academic research paper: requirements, deadlines and marks.
Academic Research Paper Requirements:
Following are the requirements for the academic research paper:
a) Paper Length
Your paper should not be less than 6 pages and not more than 12 pages.
b) Quality of Writing
The clarity and style of expression, the degree to which your paper obeys the rules to formal academic grammar, punctuation, spelling, formatting details like paragraph indentation and location of page breaks, are part of quality of writing. Write and edit your paper carefully for good organization, clear language with good spelling, punctuation, etc.
Your academic research paper must have these sections: Abstract, Introduction, Related Work, Analysis and Conclusion. You must have to follow IEEE format strictly. The format is available in MS-WORD format (Click here to download). No academic research paper will be accepted without mentioned format.
You must have to study published research papers (minimum 10). The references of published research papers and books are allowed. Any unauthorized materials’ references will not be acceptable.
You can access Research Papers on your VULMS account using link [HEC Digital Library], Google Scholar and other online free research paper repositories.
Submission and Deadlines
Students are required to finalize and submit their academic research paper by February 12, 2016.
As the academic research paper carries 15% of the total course grade, therefore it must contain implementation results of the proposed research idea. Similarly, in case of a review paper the “Discussion” section must contain student’s comments/conclusions and future research agendaregarding the domain being reviewed.
Students will be required to give presentation (through Skype/TeamViewer/Recorded-presentation etc.) of their academic research paper, well before final-term examinations. The detailed schedule for the presentations will be communicated with the students later. The presentation accounts for 5% marks of the total course grade.
Students can do this assignment in groups but in that case their academic research paper must be of high quality justifying the efforts of all the members in the group.
Warning: Write in your own words, do not copy-paste. Plagiarism is not acceptable. In case plagiarism is found, you will be awarded zero marks. No excuse will be accepted in this regard. For further understanding about plagiarism, please follow the links:
For further information and guidelines on writing a research paper, please follow the link:
Please Discuss here about this assignment.Thanks
Our main purpose here discussion not just Solution
We are here with you hands in hands to facilitate your learning and do not appreciate the idea of copying or replicating solutions.
The quality of your requirements can make or break your project. Good requirements give you control over your project development and prevent rework. Less rework means your project has a much better chance at on time and on budget delivery. All that adds up to project success and high customer satisfaction.
Let’s look at each of these in more detail…
Meeting a specific need
A requirement is a basically a statement of something someone needs. The something is a product or solution that performs a service or function. The someone may be a company, a user, a customer, support, testers, or another product.
For example, a company needs a manufacturing machine that stamps out widgets, or they need a certain plastic to feed a manufacturing machine that they already have. A bank must process debit card transactions. Alternatively, a requirement is a statement of a characteristic of something someone needs. Proceeding with these examples then, a machine must stamp out 60 widgets an hour. The raw material must be formed in sheets, or it must be red in color. A bank must process at least 1,200 debit card transactions in one hour.
Generally, you must distinguish between needs and wants. Even if it is verifiable, attainable and well-stated, a requirement that is not necessary is not a good requirement. The definition of need will depend on the context or circumstances. For instance, if you are spending taxpayers’ or shareholders’ money, need will be narrowly defined. For commercial products, a consumer want is a need for your product when it tips the consumer’s buy decision in your product’s favor.
A requirement must state something that can be verified by inspection, analysis, test, or demonstration. As you review a requirement, think about how you will prove that the product meets it. Determine the specific criteria for product acceptance, which will ensure verifiable requirements.
The requirement must be attainable. It must be within the budget and schedule and be technically feasible. Don’t write requirements for things that cannot be built or that are not reasonably within the project budget. If you do, it’s a waste of time and effort.
Many feasibility questions will not necessarily be clear-cut. You may not have the expertise to judge whether a requirement is technically feasible. If that is the case, make sure you include members of the development team in the review process to foresee technical problems. Your team may need to conduct research to determine a requirement’s feasibility before it is added to the product baseline. If this research still leaves you uncertain about the feasibility of what you want, consider stating the need as a goal rather than as a requirement. If you can’t back off to a less demanding but obviously feasible requirement, you will have to identify the requirement as a risk and monitor it with other risks and issues throughout the project.
A good requirement cannot be misunderstood. It expresses a single thought. It is concise and simple. The more straightforward and plainly worded, the better. Use short, simple sentences with consistent terminology for requirements. If possible, decide on specific names for your solution or product and deliverables and refer to them by name alone in your requirements. Use consistent language. As you define subsystems, name them also and refer to them only by those names. Use acronyms if you have to in order to keep them short. The less complex and more consistent everything is from requirement to requirement, the better. Too many words and too many references breed inconsistency and confusion.
go to this URL
click on ur required code
then click"Course Overview"
See topic and concerning Slides
select any topic and search here
read Abstract of research paper
If u think , it is related ur topic and u able to understand it
download it, download 2,3 related research papers aur bs mila k likh do
important chez: wording apni use kraen, references 15, page 6, text farmating etc IEEE ki mutabiiq honi chahiy to number 70 to 85 a jaty hain
Dil nai chorna Term paper kisi ko b nai ata hota aur na e smj ata bs likhna hota to bs likh dalaen
EndNote software download kraen, usy use krna sekhaen ye sb google sy aur youtube sy easiliy mil jata
EndNote software reference arrange krny ka kam ik min main kr deta