Updated: Oct 28, 2019
Ex 21.4
Q: Explain why an object-oriented approach to software may not be suitable for real-time systems.
A: Real-time system correctness depends on not only the results but the time at which they are produced. The concept of valuing timing for the correctness is not an attribute of the object-oriented approach. Object-oriented designs may create unreliable timings due to processing inheritance and hierarchical structures that may not be apparent at first look.
Updated: Nov 2, 2019
Our team has been making steady progress by dedication time to the project weekly. My primary area of contribution is based on test cases, documentation, and modeling.
Here are the methods we decided to make our test cases from:
glucosio-android -> app -> src -> main -> java -> org -> glucosio -> android -> tools -> GlucosioConverter.java -> ...
1. kgToLb(double kg)
2. lbToKg(double lb)
3. a1cToGlucose(double a1c)
4. glucoseToA1c(double mgDl)
5. glucoseToMmolL(double mgDl)
6. glucoseToMgDl(double mmolL)
7. round(double value, int places)
I have reworked the test cases a few times in collaboration with my teammates, Dwayne and Jason, who have been working on the driver. I thoroughly enjoy creating our team's visual models and developing formal documentation by ordering our thoughts.
Here is our project's architecture:
I am pleased to say we have stayed on track by dedicating a couple of hours to the project consistently. Here is more information on our project, as we prepare to present deliverable 3!
https://github.com/shefaliemmanuel/Lamp
Updated: Oct 28, 2019
Ex 20.10
Q: You work for a software company that has developed a system that provides information about consumers and that is used within a SoS by a number of other retail businesses. They pay you for services used. Discuss the ethics of changing the system interfaces without notice to coerce users into paying higher charges. Consider this question from the point of view of the company's employees, customers, and shareholders.
A: I believe this is extremely unethical. From the view of the company employees, even if they feel that this is unethical they might not be willing to speak out about it for job security reasons which put them in a tough position. From the view of the customers, this could give the software company a bad reputation for hiding information causing the customer to not trust them or take their business elsewhere. From the view of the shareholders, as long as they are still making a profit I can not imagine why they would mind.
At some point the unethical higher charges will be revealed which is when the employees will have this poor software engineering ethical problem the will tarnish their professional record, the customer will feel upset and betrayed, and the stakeholders will claim that they were unaware of the situation and avoid blame at all cost.