![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
For this week's conference, respond to the following:
I chose the article Why Software Fails (Charette, R. N., 2005). This article is a little bit old, but even now I often hear that unfunctional and buggy business software costs too much.
In my opinion, because there is no bug-free software, I suggest that you build of a management system that allows to detect and fix software bugs early. The same applies to hardware as well. You need to architect systems based on the idea of design for failure.
In addition, you should try not to write code as much as possible, and make the very minimum of software. In other words, you actively use exist and mature software modules or components including open-source software and Web APIs.
Charette, R. N. (2005). Why Software Fails. IEEE Spectrum, Retrieved on August 23, 2015 from http://spectrum.ieee.org/computing/software/why-software-fails
Here is where you discuss with each other topics you are interested in, and what role you would like to play in a project with the goal of forming at least tentative groups by the end of the week.
By the end of this week, you should have pretty well decided on the project topic for your group, posted it here, and gotten my agreement.
I would like to play a role as a developer or a systems architect. Because English is my second language, playing a leading role seems to be difficult for me. I have a project idea that is a building a Web scraping client app in in Java or Scala. The app allows you to automatically extract information in DOM or CSV from a website that requires you to log in with a username and password.
As Luis posted my introduction to the Introductions thread, my skill sets are as follows.
I have more than 4 years of working experience as a technical sales representative. I directed of more than 50 projects including offering managed server hosting, cloud systems migration, integration, and 24/7 operational monitoring using cloud services such as AWS, and design/implementation/operations/consulting business/consumer applications for PC, feature phone, and smartphone/tablet as a technical consulting sales representative and a project leader.
For this week's conference, respond to the following:
Instructions
Your Project Plan should include an outline of the key milestones for your project and who will achieve them.
Requirements Specification:
What is this project supposed to do? Be as specific as you can The specification should include scenarios or Use Cases (HINT, HINT)!
System Specification:
Hardware and software base for your project. A PC with a JDK is reasonable, but you might add more details, or make other selections, as appropriate. For example you might specify a web server with PHP , or the Android SDK, Android Studio and a Genymotion emulator.
Discuss the Project Plan and assign sections and responsibilities in your group. A group Discussion area will be posted early this week to facilitate your discussion. You should all submit a Project Plan to your Assignment Folder, but each group member should submit the same Project Plan.
When we analyze software requirements, we have to analyze not only functional requirements but also non-functional requirements. Sometimes both software developers and customers tend to miss non-functional requirements when a software development project is initiated.
Since it causes that we perhaps unintentionally have an enormous gap with customers, we want to consider non-functional requirements for our software development projects as well.
Svensson et al. interviewed eleven companies which includes both B2B and B2C companies on software quality requirements. According to the article, prioritized types of quality requirements are different depending on whether software users are business users or consumers
Figure 1: Importance of quality aspects in the article shows that usability is the highest prioritized quality aspect for consumer software. It is followed by performance requirements and stability. On the other hand, for business software, safety is the highest and it is followed by performance, reliability, and stability.
As mentioned in the article, we can reference some common indications of non-functional requirements such as McCall's quality model and ISO 9126.
Berntsson Svensson, R., Gorschek, T., Regnell, B., Torkar, R., Shahrokni, A., & Feldt, R. (2012). Quality Requirements in Industrial Practice-An Extended Interview Study at Eleven Companies. IEEE Transactions On Software Engineering, 38(4), 923-935. doi:10.1109/TSE.2011.47
