Important Difference Between Generic Software Product Development And Custom Software Development4/13/2019 Gundam vs. zeta gundam gamecube iso. An NDA for Software Development is Critical but NDAs are undoubtedly important, but let’s put that concern in its proper context. A software development companies‘ skills and focus are primarily on providing development services to their clients. Best Answer: generic, or out-of-the-box, software is made to sell to a large ammount of people (i.e. Microsoft office) whereas custom fortware is made for one person/company, to their exact specification. It is more expensive, but it means your software does exactly what you want. In a typical SDLC there isn't much mention of the word production or development or the distinction between the two.These seem more of a real time, industrial driven concepts. I have come across these terms in regards describing companies. As i understand Production in Software does not necessarily mean product development.Inspired from the question I came to question the basic distinction between the two i.e development and production in regards to software. I used to be under the impression it was just a way of describing the development process in a product development company. • Question 1: What is the distinction between the two? • Question 2: How widely are these terms used? And are they properly understood and distinguished? • Production is where the 'rubber meets the road'. It is no longer a 'controlled' environment where the only people who know how to use it will interact with it (developers, QA, Product.). There will be users who are using that software for the first time, and have their own assumptions and prejudices. The performance, scalability, logging, monitoring, security are a few things that will be much closely watched when the software is in production vs. When it is under development. • These term 'Production' is very common and anyone who has seen a software pass through the engineering process knows it. However, there are synonyms for other steps in SDLC - usually it is requirements gathering, design, implementation (coding), testing, release and maintenance. As you can see release is where production comes in. Release is a generic term - first, software is released to QA for acceptance testing release. Once QA accepts/approves it, you have a choice to release it in an alpha mode, where 'eat your own dogfood', internal users start using it. Beyond alpha, there is beta where the system is still released but to a little more wider set of audience, like early adopters or people who volunteered to participate it in. Finally it comes out of beta and is released as GA. Usually GA is called Production or 'Stable' release. – Apr 14 '11 at 18:48. • Tutorial • Lab • This Tutorial is based on questions from the book Software Engineering 10 by Ian Sommerville and is based on the material covered in chapter 1. Week 2 Tutorial 1) What is the most important difference between generic software product development and custom software development? What might this mean in practice for users of generic software products? Give some examples of generic software products that you have used? Give some examples of custom software products that you have used? In terms of jobs roles what type of software product do you think you will end up developing? 2) What are the four important attributes that all professional software should have? Suggest four other attributes that may sometimes be significant. 3) Apart from the challenges of heterogeneity, business and social change and trust and security, identify other problems and challenges that software engineering is likely to face in the 21st century (hint: think about the environment). 4) Based on your own knowledge of some of the application types discussed in section 1.1.2 of Software Engineering 10 explain, with examples, why different application types require specialized software engineering techniques to support their design and development. 5) Discuss whether professional engineers should be certified in the same way as doctors or lawyers. • Week 2 Lab Exercise: Historical Perspectives In this set of lab exercises you are required to use the library search facilities to track down a couple of historic papers on topics related to software engineering. The link to IEEE explore is given below. Use IEEE xplore to find the following journal article. Brooks, F.P., No silver bullet, Essence and accidents of software engineering, IEEE Computer 20 (4), April 1987. This is quite an old article. Read through the paper and make notes. IN around 250 -350 words record what you expect to learn from a module entitled Fundamentals of Software Engineering and in particular how you might use these skills in the future. Use IEEE xplore to find the following journal article.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |