Your manager is quite impressed with the security considerations you explained to her thus far; however, she asks that you give further thought to additional security measures where possible, and to develop a memo citing those additional safeguards. Complete the following assignment:
Write a ½ page memo describing additional security considerations you would add to a requirement definition in addition to those outlined in Chapter 7.
Feel free to utilize outside (online) sources to expand your list of necessary security measures.
Be sure to cite any sources.
Your memo should be professionally written and should not simply be a restating or paraphrasing of the sources researched or the textbook. It should be a personal view of the issue and your ideas on how to avoid them.
You did the one last week for me. Can you continue on with it ? I have attached it for reference. Also please be original in the content and cite any resources used.
January 20, 2016
To: Mr. Tuew Dewiere
From: Smith Jone, CTO
Subject: Regarding Use of programming language .NET
Asp.net is some piece of the entirety. NET structure, based on top of the Common Language Runtime (otherwise called the CLR) - a rich and adaptable construction modeling, planned not simply to cook for the needs of engineers today, however to take into account the long future we have in front of us. What you may not understand is that, not at all like past redesigns of ASP, Asp.net is truly more than simply a redesign of existing engineering – it is the passage to an entire new time of web improvement.
Asp.net has been intended to attempt and keep up language structure and run-time similarity with existing ASP pages wherever conceivable. The inspiration driving this is to permit existing ASP Pages to be at first relocated Asp.net by basically renaming the document to have an amplification of .aspx. Generally this objective has been attained, in spite of the fact that there are normally some fundamental code changes that must be made, since VBScript is no more underpinned, and the VB dialect itself has changed.
The .NET Framework incorporates another information access engineering named Ado.net, an evolutionary change to ADO. In spite of the fact that the new information access innovation is evolutionary, the classes that make up Ado.net look somewhat like the ADO objects with which you may be recognizable. Some reasonably huge progressions must be made to existing ADO applications to change over them to Ado.net. The progressions don't need to be made instantly to existing ADO applications to run under Asp.net, in any case.
In end, I would like to conclude that the use of .NET for project development by the team is good decision but only in those cases where it will not affect the financial position of the company as a whole. Other factors are also relevant so they should also be considered while making the decision.