Abstract: The invention provides a urine sensing device and methods therefor to estimate the volume of urine in a bladder in a non-invasive, real time manner. The urine sensing device comprises plurality of drive electrodes and sensors configured to be positioned in contact with or proximal to skin of the abdomen region of a human such that the relative positions of the drive electrodes and the sensors are known. The plurality of drive electrodes are capable of exciting the abdomen region with an electrical current comprising a plurality of frequencies. The plurality of sensors are capable of measuring at least one electrical parameter from each of the plurality of drive electrodes and the plurality of sensors. Based on the measured values of the at least one electrical parameter, the volume of urine in the bladder is estimated, while taking the electrical conductivity from the bladder tissue, skin, and other extraneous factors into account.

Abstract: The technique relates to a system and method for generating billing data of a composite cloud service. The technique tracks and meters manual service usage along with the infrastructure and software usage to generate billing data for the composite cloud service. The technique involves receiving a user request for the composite cloud service. After receiving the user request, one or more infrastructure, software and manual resources required to fulfill the user request are provisioned. Thereafter, the consumption of the one or more infrastructure, software and manual resources in real time to fulfill the user request is measured based on a predefined monitoring metrics. Finally, billing data for the composite cloud service is generated based on the measured consumption data of the one or more infrastructure, software and manual resources, a predefined chargeback model and a predefined billing policy.

Abstract: Described herein are methods and systems for capturing functional and non-functional requirements of a software system. Both functional and non-functional requirements are captured in a framework that is easy for end users to use for participating directly at various levels of a requirements capture process. Functional aspects are desirably captured in terms of workflow notations to form a task flow model of the system, which in turn provides a desirable framework for eliciting and appropriately capturing the non-functional requirements. The task flow model updated with functional and non-functional requirements can be comprehensive and accurate enough to be used to generate test cases, to simulate usability and to generate conventional text based use cases. The requirements captured can be verified for quality of domain context to encourage re-use of domain terms.