代写商科论文

汉密尔顿论文代写:软件需求规范

汉密尔顿论文代写:软件需求规范

在编制SRS时,指定了用户特征、用户期望等。随着项目的开发,这将成为测试规范的一部分。关于软件需求规范有四个要点,在这四个要点中定义了项目。项目需要利用实时反馈系统和预约系统。它需要一个帮助台或一个用户支持系统以及一个库存审计系统。我在分配工作中面临的主要挑战是,我觉得项目的不同源需求太复杂,不能作为一个源需求来表示。我有一些实习经验,我观察到在现实的项目中,很多的项目在一个项目阶段是不会被接受的。如果是的话,以后会有很多测试和修复。因此,为这样一个大项目准备需求规范对我来说有点令人生畏。

汉密尔顿论文代写:软件需求规范
所以我认为最好的方法不是把注意力集中在项目的所有任务上,因为每个任务下都有很多子任务,这些子任务本身可能就是一个项目。其次,在以这种方式开发每一个任务需求时,还存在一些问题,供应商可以提出解决方案。我相信,对于我在RFP中编写的每一个功能性业务需求,我都可以以更多的方式进行批评和扩展。如果RFP不详细且写得不好,那么它可能无法回答供应商的某些查询,因此会失去目的性。在未来,当我从事需求规范的工作时,我将确保所有不同的规范细节都被识别并被很好地收集。

汉密尔顿论文代写:软件需求规范

In preparing the SRS, specified the user characteristics, user expectations and more. This would form part of the testing specifications later on as the project is developed. There are four main points about software requirements specification, and in this the project is defined. The project needs to make use of a real time feedback system and booking system. It needs a helpdesk or a user support system and also a stock auditing system. The primary challenges that I faced in my allotment of the work was that I felt the different source requirements for the project were too complex to be presented as one source requirement. I have some internship experience and I have observed that in real world projects, so much of roll outs would not be accepted in one project phase. There would be much testing and fixing later if it was. So in preparing a requirements specification for such a big project as such was a little daunting for me.

汉密尔顿论文代写:软件需求规范
So I believed the best way to achieve it was not focus on all the tasks for the project, as in there are so many subtasks under each task which could hence be a project by itself. Secondly, there are also issues in the form of developing each of these task requirements in such a way, that the vendor can propose solutions. I believed for each of the functional business requirements that I wrote in the RFP I could very well critique and expand upon in many more ways. An RFP that is not in detail and not well written might fail to answer some of the queries of the vendors and hence would lose its sense of purpose. In future when I work on requirements specifications I would make sure that all the different specification details are identified and are well collected.